How to make trigger conditions branch friendly ?

Zein Makki

Hello,

Scenario: We have a main bamboo plan (Source Build) that runs the source code build. We create a branch out of that.  We have other long running integration tests that also have branches configured. This looks like the following:

• Source Build (master)
  • Source Build (Branch A)
• Feature A (master)
  • Feature A (Branch A)
• Feature B (master)
  • Feature B (Branch A)

We have scheduled triggers to run the integration tests multiple times a day. Now we chose the trigger condition to Only run Build if other Plans are currently passing and provided the plan key for plan (Source Build).

 

Now, it makes sense for Feature B (Branch A) to get triggered only if Source Build (Branch A) is passing successfully which is not the case. It seems that this trigger condition only checks for  Source Build (master).

Is this by design ? What is the rational behind this ? And is there any way to achieve the described behavior ?

Gonchik Tsymzhitov

Hi! 

 

I have read your question, I can only suggest  you try use this one (child plan)

https://confluence.atlassian.com/bamboo/setting-up-plan-build-dependencies-289276887.html

or write in plan as final stages some automatisation based on rest api call https://docs.atlassian.com/atlassian-bamboo/REST/latest

 

Cheers,

Gonchik Tsymzhitov