In our older bamboo 3.4.3 instance, I used to define some build plans that depended on a parent plan, which allows the parent plan to complete and report its completion, and then the child plan would start. This was convenient, because the child plan did work that the parent didn't need to wait for, and the child plan takes much, much, longer than the parent.
Today I'm trying to create a similar structure in Bamboo 4.4.5, but on the "Dependencies" page, which in the old Bamboo listed all the plans this plan could depend on, either as a child or a parent, it now doesn't list anything.
It appears my only choice is to go into the parent build plan and set this other plan as a child plan. It doesn't say either way whether the child plan will be started asynchronously with respect to the parent plan, which is effectively how it worked with the old Bamboo.
Ironically, on the new Dependencies page, it specifically says "You can configure this Plan to trigger child Plans or be triggered by parent Plans on this page." The second part of that sentence refers to the functionality we had in 3.4.3, but it's not giving me that ability in 4.4.5.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs