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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo child plan triggering - multiple parent plans successful builds

I would like to trigger child plan where multiple parents have successfully built the plans.

I can trigger child plan based on one parent successfully built but I would like to add dependency for 2 parents.

Can someone from the community help to solve this issue?

 

1 answer

0 votes
Bill Carreon Atlassian Team Apr 30, 2018

HI Pankaj,

 

If you need a plan to trigger, let’s call this plan C after 2 other plans have successfully run, let’s call these Plan A and Plan B, you can set up a daisy-chain dependency. That is to say that you can have Plan B run if Plan A is successful, then trigger Plan C on Plan B’s success,

 

Plan A -> Plan B -> Plan C

 

This will ensure Plan C is run only if Plan A and Plan B have been successfully executed.

 

Best Regards,

Bill

Hi @Bill Carreon,

is this the only possible solution for this kind of problem? Because if you're having multiple parent dependencies, like 20-something, the chain gets really long and slow. Also parallelism with mutliple agents isn't possible.

We tried setting "Dependency blocking strategy" to "Block build if parent plans have unbuilt changes " (which I think only works for code commits), as well as "Trigger conditions" set to "Only run Build if other Plans are currently passing" (and provided a list of all parent plan keys). Both doesn't seem to resolve this problem of depending on ALL parent plans being green.

If it's not possible to achieve this right now, is there anything planned in the future?

Thanks and Best Regards,

Felix

PS: We're using bamboo 6.2.5

Any update on this? We have a similar issue where we have multiple modules that get built, and a child plan that puts together a docker image pulling in artifacts from all the parent builds. We would like to have the docker image built only once after *all* the parents complete building, not after each individual one

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

703 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you