Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can you limit the number of concurrent builds in pipelines?

We're trying to run Maven builds that deploy to a specific set of servers using Pipelines. One potential problem we've encountered is that if multiple users commit and trigger concurrent builds, it may cause problems with deployment.

Is there any way to limit the number of concurrent builds for a branch or force them to run sequentially? Or can we set things up to run just one build at a time?

3 answers

Also, I have one specific step which I don't want to more than one pipeline being executing at the same time. Something like jenkins lockable-resources would be super useful !

That is what we use in Jenkins too

gitlab has `resource_group` option
it'd be nice to have something similar for bitbucket

0 votes
Tom Bradshaw Atlassian Team Oct 09, 2016

Hi Daniel,

Unfortunately there is no way for a user to specify a limit on the number of concurrent builds. However, we're interested in what you need in this feature. If you'd like to raise a ticket at we'll have a look at this feedback when considering our roadmap.

Hi Thomas,

do you know if there was a ticket raised? I would need exactly the same feature because concurrent builds will cause issues for example when running our integration tests (database reset at start) and for those tests we also deploy our application within the pipeline which is also causing problems when two builds deploy at once. That feature would be really helpful.




I am also interested in this. In my case builds should never run concurrently instead they should be queued and executed following timeline of commits, so I would set this number to 1 always if there was such setting. However if you don't do this using queues already I don't think temporary solution of limiting concurrent builds is good idea as some builds can be missed that way.


This would also be needed for doing database migrations and for release/version/tagging.

We still use Jenkins for database builds for this exact reason. Plus, we have to limit PR merging to master to allow the Maven Release plugin to finish before merging another PR.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,927 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you