+1

+99999

+1

this feature is very important for testing purpose.

+1

+1

+1

+1

+1

+1

+1

Why is such an important and voted issue opened from 2008? Should we migrate to TeamCity?

A rather clunky workaround documented on stackoverflow http://stackoverflow.com/questions/36538061/bamboo-limit-concurrent-builds-across-branches might help some users in the interim...

Seeing another important feature lurking around for a very long time just beeing ignored by Atlassian makes me very sad indeed.
This one is even in the Top 50 of most voted issues.

+1

+1

For the love of god (or deity of your choice)... someone make this happen!

I wanted to add my voice that this is a very important feature for a mature CI tool to have. Please implement it soon!

Judging by Atlassian's [lack of] response, I doubt we'll ever have it, Carl.

Surprised that this is still not available in Bamboo.

+1

We have a set of test builds that hit the same resources heavily. We don't want to run them at the same time. Nothing currently in Bamboo allows us to do this so we're stuck babysitting the builds manually.

+1
We really need a "Don't Build Concurrently With" plan option. It's a missing core feature, really
Shouldn't be hard to implement

+1 to get this into Bamboo.

Charles' plugin doesn't work as smoothly with newer versions of Bamboo and so we're getting "stuck" here. This happens frequently:

Step 1 : Test build prepares environment
Steps 2-10 : Tests run in parallel against environment

We have multiple Plans which do these steps. If step 1 is run on another plan while steps 2-10 are running, then that re-initializes the environment and prevents the tests from running properly.

I had a quick look into it, but it seemed like getting the plugin onto the marketplace was going to be too many hoops to jump through for such a simple, free plugin. Maybe someday if it proves popular and I have the time.

Thats great Charles. Are you planning to get this onto the Atlassian Marketplace at all?

I implemented a simple plugin to solve this problem a while back and have just gotten approval to open source it. Source and documentation can be found here: https://github.com/ampedandwired/bamboo-mutex-plugin.

This would still be better implemented within Bamboo core I think, but this plugin should do the job until then.

I would like to reiterate how important this is to my team. It's been 31 weeks since I posted our wish for this to be implemented, but I don't want to leave the impression that we have a workaround or that everything is getting along fine without this fix. We are no better off here, and the problem is now five times worse because we have so many more plans and builds in process. I don't know what it might take to convince Atlassian to make this happen sooner, but please don't let lack of continued comments lead anyone to believe that things are better.

We also need atomic plan execution. If three different builds on the same agent are concurrently executing, it makes the build completion time a useless statistic, not to mention all of the complications above.

We would like to be able to avoid the interleaving execution of jobs from diffent plans. It is causing us a number of problems without any workaround at this time.

We have the exact same problem: Different plans that use a shared resource, but are otherwise independent, are allowed by Bamboo to execute interleaved/intermixed jobs, on a given agent. This causes problems, and we would like to somehow make sure that those plans are not allowed to interleave the execution of their stages/jobs.

I vote for a solution

Thanks for the clarification.

Hi Anton,

Sorry for not making this clearer.

By atomic I mean that the plan should run all stages on a particular agent before any other plan gets to run any stages on that agent. At the moment stages are atomic, it would be nice to allow plans to be atomic also.

HTH,

Paudi

Hi,

I am not sure what you mean by "plan execution is not atomic".

If Concurrent Builds are disabled, then a single plan would never execute concurrently, therefore plan execution is atomic.

If Concurrent Builds are enabled then the build execution is not atomic.

Do you mean you would like us to make the Concurrent Builds documentation more prominent?

Cheers,
Anton

Thanks Anton,

I've been struggling to have this understood for a while. In the meantime, a note in the docs to make it clear that plan execution is not atomic might prevent further confusion. I certainly assumed it would be.

Thanks for the update. I certainly see what you mean.

Dependencies are not a good fit. My plans are not interdependent in the usual sense, they just share a resource and may conflict if they are not executed atomically. Using Bamboo dependencies, I would have to make one plan a parent and another a child. This would cause unnecessary building as the parent plan would trigger the child plan(s).

I can certainly work around the problem and avoid the conflict by modifying the source code. I already said this was a problem of convenience rather than ability:

It is convenient to have these plans build the same database but interleaved stage execution prevents this.

You can't implement the ordering that you need via dependencies?
Or wire something into your Test fixture to check the resource you're depending on and its state? READY/NOT_READY, etc?

This could also prevent interleaved execution of stages from different plans.

I have multiple plans (trunk, branch A, etc) which build a database in stage 1 in preparation for stages 2,3,...

It is convenient to have these plans build the same database but interleaved stage execution prevents this.

Would be nice to be able to disallow this.