We have a branch pipeline that creates a new git tag. If multiple PRs get merged at around the same time, this branch pipeline is started multiple times. Now there could be race conditions, where the pipelines are failing, because the previous ones have not finished pushing the new tag.
Is there a way to let a branch pipeline wait until the previous one has finished?
Hi Marcus,
You could use deployments for certain steps of the branch pipeline:
At the moment, this is the only way to prevent certain steps of different pipelines to run at the same time. If a deployment step is running, then deployment steps to the same environment from subsequent pipelines will be paused. Please keep in mind that paused deployment steps will need to be resumed manually, there is no automatic resuming.
We have a feature request for automatically resuming paused deployment steps:
You can check the pinned comment in that request from one of Bitbucket's product managers and provide feedback, this is something our team is planning to work on.
We have a different feature request for concurrency control in non-deployment steps that you can also vote for and leave feedback:
Please feel free to let me know if you have any questions.
Kind regards,
Theodora
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.