Historically, Gearset has allowed the creation of any number of pipelines for the same code repository.
Recently however, we have seen a number of hard-to-diagnose issues that have been traced back to this sort of set up.
In order to avoid users inadvertently creating scenarios where we know these failures can happen, a check has been added to prevent the creation of a new pipeline if there is already an active one for the same repository:
The most likely cause of a problem is a race condition between webhooks. For example, when a pull request is merged, a webhook will be fired to let Gearset know.
If there are 2 different pipelines that are both using the target branch as a static environment then they will both start processing this webhook simultaneously.
This can lead to issues such as git commits or jira comments being made using unexpected user accounts, missed pre/post checks and duplicated or missed validations/deployments to name just a few.
If this check is preventing you from doing something that you need to do then please let us know. We'd love to hear about your use case and there are a couple of potential workarounds we can discuss.