Possible to trigger dependencies one by one?

Question

Hi,

I have a set of build jobs that I want to trigger from one parent build job. However, I only want them to run one by one, since they are technically deploy jobs (but defined as build jobs in Bamboo) and deploying more than one module at a time creates race conditions and breaks things. So I want to have the following:

Parent plan, having dependencies:
-> plan A
-> plan B
-> plan C

Where if I run "Parent plan", then plan A, B and C are all triggered - but only run one at a time (ordering does not matter). I have multiple agents that can run each plan, and would prefer to not limit it, since running steps (within stages) in the plans in parallel shortens down build times.

I could daisy-chain them together (Parent triggers A, A triggers B, etc), but this has the issue that running plan A separately starts the chain of running B, then C, etc. - which I don't want.

Is there some way of specifying "run these dependencies, but not in parallel"?

unknown · Answer

Hi,

Thanks, I'll have to look into this solution. From what I gather then, something like this is not available directly from the Bamboo web UI?

If not, I think it would be a handy addition to just have a checkbox option under "Dependencies" for "Run in sequence" and "Wait for each child plan to complete before running next". I would guess I'm not the only person to have this use case.

unknown · Answer

Hi,

Thanks, I'll have to look into this solution. From what I gather then, something like this is not available directly from the Bamboo web UI?

If not, I think it would be a handy addition to just have a checkbox option under "Dependencies" for "Run in sequence" and "Wait for each child plan to complete before running next". I would guess I'm not the only person to have this use case.

Eduardo Alvarenga · Answer

Hello @[deleted], Welcome to Atlassian Community!

You can have a "master" Plan that would trigger Plan A, B and C via Bamboo REST API from a Script task.

Each build would be independent, so it would be important to have a second Task that would be used to validate the results of every build.

Queue a build:

* https://docs.atlassian.com/atlassian-bamboo/REST/8.1.3/#d2e4982
* Make sure to capture each resulting buildNumber

Query build results:

* Have the buildNumber for each build use the API again to monitor the results
* https://docs.atlassian.com/atlassian-bamboo/REST/8.1.3/#d2e4105

An interesting blog article describes this strategy:

* BAMBOO REST API: HOW TO TRIGGER A PLAN AND WAITING FOR A RESULT

Regards,

Eduardo Alvarenga
Atlassian Support APAC