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?
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 https://bitbucket.org/site/master/ we'll have a look at this feedback when considering our roadmap.
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.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs