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'.)
Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...