Due to the behavior of deployment concurrency control, when a new pipeline is started while a previous one is running, the new pipeline is paused. It would be ideal to have the ability to automatically resume the most recent paused pipeline once the current pipeline has completed.
I am aware that a paused pipeline can be resumed manually from the web interface, but having the option to start the most recent paused pipeline automatically would make the whole process a lot easier.
For example, our repo is set up to run a pipeline whenever someone commits to our development branch. If three people commit to that branch within a few minutes of each other, the first pipeline will run and complete, but the next two will not. Ideally, the most recent pipeline would automatically resume once the first pipeline completes, ensuring that our most recent commit is tested properly.
I've tried using the REST API to start a new pipeline in the after-script section, but since the pipeline is still running, the new one gets paused again.
Is there any way to accomplish this behavior?
Please find this feature request, this may cover what you're looking for:
https://jira.atlassian.com/browse/BAM-21281 this is a better feature request, although directed at Bamboo, but the solution and behaviour expected is actually the same for Bitbucket Pipelines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.