Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,902
Community Members
 
Community Events
176
Community Groups

Possible to trigger dependencies one by one?

Edited

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"?

2 answers

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.

0 votes

Hello @Espen Kristensen, 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:

Query build results:

 

An interesting blog article describes this strategy:

 

Regards,

Eduardo Alvarenga
Atlassian Support APAC

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events