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

What is the impact of setting concurrent builds to 1?

james_mckean February 1, 2024

Sometimes I think myself into a corner.  When you enable Bamboo's Global Concurrent builds and set the value to 1, does that mean only 1 build of the same plan will run at the same time or only 1 additional build will run?  

I ask because we configure our build plans with stages that deploy the build artifacts rather than using separate deployment plans. So most of the time, we do not want to run more than 1 version of the same plan concurrently.  The default has worked well for us.  But now we have a plan that does not deploy but is called by multiple other plans to update certain metrics that we track.  We would like these plans to run concurrently.  Because the parent plans pass different variables to the metrics plan, there is no problem with them running concurrently and no danger of them over-writing one another.

So my idea is to set the global concurrent value to 1 and the specific metrics plan to some value > 1.  I apparently need to enable global concurrency and set the global value to something for the plan-level concurrency option to appear.

Does this seem reasonable?


1 answer

1 accepted

1 vote
Answer accepted
Shashank Kumar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 2, 2024

Hello James,

If you set the Global Concurrent builds and set the value to 1 it means at a time Bamboo will run only 1 build for the plan, if you want Bamboo to run 2 builds for this plan at a time, you need to set this value to 2.

I agree with what you are planning you can keep the Global value to 1 and change the value for that particular plan. This seems reasonable to me. 


Shashank Kumar

**please don't forget to Accept the answer if your query was answered**

james_mckean February 15, 2024


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events