Looking at the documentation, I think there's a strong argument to be made that this issue is not, in fact, fixed. From the docs:

Please note, dependency blocking only works when triggered by code updates (i.e. polling or check-in). It will not work when a build is triggered on a schedule or triggered via a parent build (when there are multiple parent builds in progress).

For this issue, that means that project A is still going to be built twice as parent builds B and C each trigger builds of A that ignore the dependency blocking strategy.

I really have no idea why you would implement dependency blocking this way, but it makes it pretty useless.

Hi guys,

Thanks for the patience on this. With Bamboo 2.3, we have implemented the dependency blocking which should resolve this problem.

Cheers,
Edwin

I agree that this is the largest issue we have with bamboo. We have a number of projects which are building multiple times because of similar cases. Is there any plan to remedy this? It would just need to mimic functionality as seen in maven's module handling. When a build triggers, make a queue of builds in the correct order and work your way through them.

I think there's a strong case to increase the priority of this defect, to at least critical. It makes Bamboo's implementation of dependency builds effectively un-useable for real-world code bases.

In my opinion this is the biggest flaw in Bamboo as a professional build system. While being able to act on Maven dependencies would be even better, this seems like it should be a simple improvement.

Right now we either have to:

1. Manually build dependencies (error prone and time consuming)
2. Suffer through 10+ sequential builds of our project, and the fact that this blocks other builds waiting in the queue
3. Create and maintain super-projects using svn symlinks to build it all on in single plan using a parent POM. This project rebuilds all the time, and since it includes many projects the build is slow.

Hi Craig,

Thank you for your suggestion.

I suspect this issue is very much related to BAM-1844 - if not the same use case, the general idea is that, Bamboo should handle more complex dependent builds.

This is a popular feature request and one of the things that will be looked at post Bamboo 2.0. I will update this issue once its scheduled for a fix.

Regards,
Ajay.