Rather than use child plans / dependencies - which will get unwieldy with the number of plans and git repos we have - I'd like each plan to declare its upward, parent dependencies.
The Plan object (and Deployment) allows you to pass in multiple triggers, which gave me hope! But I couldn't find a Trigger class for defining multiple, arbitrary parent-plan triggers.
Thank you. But this looks like another way to trigger child plans.
We are looking for a way for a plan to say, "run me after plans: a, b, c, x, y, z".
(The same way gradle and maven allow you to define dependencies for yourself. And then gradle/maven work out the build order for you using 'directed acyclic graphs'.)
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...
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