Yaml Specs support might be tracked at BAM-21262

I also miss "Only run Build if other Plans are currently passing" feature in Bamboo Specs

Thanks Alexey.

In my case the triggering condition is time (periodic check of something), so the built in "scheduling" triggers are sufficient and all I want to do is add a "condition" to say whether or not the trigger should be allowed to proceed and run/execute the plan. The "trigger condition" would be a perfect solution if it was supported by specs. Because it is not I briefly looked at trying to extend the built in scheduling triggers but quickly got lost. I'll review your code and see if that clears things up for me.

wtb, if you need sample code to create custom trigger look at https://bitbucket.org/atlassianlabs/bamboo-after-deployment-trigger/ or https://bitbucket.org/chystoprudov/bamboo-failtrigger-plugin/src/master/

Here is an example of why this is important to me:

https://community.developer.atlassian.com/t/how-to-pass-information-from-a-bamboo-build-trigger-condition-to-the-build-that-is-triggered/29337

I have spent a few moments looking at the source code for some standard triggers to see if I could switch from a trigger condition to a trigger (since they are supported by specs), but I don't see how I would do what I want to do and I get the impression that implementing a trigger is not something Atlassian expects an end user to do.

So I am stuck, since a plan that is 95% "configuration as code" does not cut it.