Bitbucket Concurrency Control

[Deb Pramanik]

Hi all,

Is there any way to automatically trigger/rerun a halted pipeline when the previous PR validation pipeline passes or fails, rather than running it manually?

[Aron Gombas _Midori_ · Accepted solution]

@Deb Pramanik 

Bitbucket Pipelines does not natively auto-resume halted pipelines when a concurrent slot opens up due to plan-level concurrency limits. However, these may work:

1. Use the max-concurrency keyword in your step definition. When configured at the step level, this causes steps to queue automatically and start when a slot becomes available, rather than being halted. In your bitbucket-pipelines.yml, you add max-concurrency: 1 (or your desired number) to the relevant step.

2. Use the Bitbucket REST API to programmatically trigger pipelines. You can add an after-script section in your pipeline steps that calls the Bitbucket API to check for and re-trigger halted pipelines when the current one finishes. The relevant endpoint is POST /2.0/repositories/{workspace}/{repo_slug}/pipelines/ to trigger a new run, or you can use PUT to rerun a halted one.

[Deb Pramanik]

Thanks, @Aron Gombas _Midori_, I will try to do this.

[Arkadiusz Wroblewski · Accepted solution]

Hello @Deb Pramanik 

Bitbucket Pipelines steps support concurrency groups, queuing steps using the same group first-in, first-out so only one runs at a time, with the next waiting step proceeding automatically upon completion of the previous one.

That's probably what you looking.

https://support.atlassian.com/bitbucket-cloud/docs/step-options/ 

Best,

Arek 🤠 

[Deb Pramanik]

Thanks @Arkadiusz Wroblewski , I will try