Can a plan declare its parent plan triggers?

[Rob Bork]

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.

[Foong]

Try Bamboo Specs to modify multiple plan dependencies

[Rob Bork]

Thank you

[Foong]

Feature request https://jira.atlassian.com/browse/BAM-14981

[Rob Bork]

yes, we are using java specs for our plans.  And really like it!   But it only does downward child dependencies (and VCS dependencies.)

I would just suggest to the Bamboo Team that they add this parent-dependency capabilities.  I think a lot of folks would find it useful.

[Rob Bork]

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'.)

[Foong]

Try this app Chain Build Tasks for Bamboo to use task to trigger another plan