You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see a lot of pipelines failing due to a pre-existing state lock, especially if both a PR and Branch end up kicking off builds in the same repo around the same time. This results in a lot of re-work, and lost time. It would be very helpful to control the behavior around this scenario to reduce the chances of a pipeline failing due to concurrent executions.
The text was updated successfully, but these errors were encountered:
I see a lot of pipelines failing due to a pre-existing state lock, especially if both a PR and Branch end up kicking off builds in the same repo around the same time. This results in a lot of re-work, and lost time. It would be very helpful to control the behavior around this scenario to reduce the chances of a pipeline failing due to concurrent executions.
The text was updated successfully, but these errors were encountered: