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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Dependent plans are not always triggered




I am trying working on implementing continuous delivery (CD) in our project and conceptually it should such that every build should cause a new release of the component and subsequently trigger any dependent component to be build with the released components included.

So in order to make this work all dependencies are formed between the bamboo plans through the dependencies tab in the configuration for each component, and in addition to avoid race conditions only one concurrency build is allowed for each component.

Let us say we formed a dependency between project A and project B, such that project A is a parent to project B and it works as expected for most cases.

However I experience whenever project B has started and something triggers project A to be build again (e.g. a push to the repository) and if project A is completed prior to the on going project B has completed no addition job is added to project B i.e. the plan for project B will not build again, and one have to manual trigger B to be build again, which kills my plan of doing CD.

I cannot make up whether this is as intended or not. (Most likely I would say it is intended, as it is also not possible to manually trigger a build on project B once project B has started).

My expectation is that triggering build of dependent plans was guaranteed once it had been formed by bamboo, however that does not seem to be the case.

In case this is intended leads to a conclusion that I may designed my CD wrongly or maybe I have not found the correct way to queue up a builds which also does not allow having concurrent builds.

Anybody who can shed some light one whether it is the former or the latter.

In cases this is intended and I have not designed my CD wrong. Are there anyway to change the behavour adding a plugin extension or something similar?


I would imagine the same holds true if something is pushed into a repository and a build already has started but not completed. But maybe due to a scan later on it will trigger the build again.

Anyway pointers would be appreciated

The bamboo version I am running is  6.3.1 build 60306




Thanks in advance

1 answer

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events