Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Wait for previous plan to finish building before starting the next one

I have set up a Plan in Bamboo (running on Ubuntu 12.04) with 3 Stages. I'm just using the default Agent.

Builds are manually triggered via a POST request to the REST API. I want builds to be able to be queued so I've set number of concurrent builds to a high value (which seemed to be the only way to achieve this), but I also want one build to finish before the next one begins.

At the moment this is what's happening if I send 3 build requests in quick succession:

  • Build #1 Stage 1
  • Build #2 Stage 1
  • Build #3 Stage 1
  • Build #1 Stage 2
  • Build #2 Stage 2
  • Build #3 Stage 2
  • Build #1 Stage 3
  • Build #2 Stage 3
  • Build #3 Stage 3

This is what I would like to happen:

  • Build #1 Stage 1
  • Build #1 Stage 2
  • Build #1 Stage 3
  • Build #2 Stage 1
  • Build #2 Stage 2
  • Build #2 Stage 3
  • Build #3 Stage 1
  • Build #3 Stage 2
  • Build #3 Stage 3

Anyone know how to achieve this? Stage 2 takes about half an hour and Stage 3 sends an email, so if 20 build requests are submitted then we have to wait around 10 hours for all of the Stage 2s to complete before the emails are finally sent all at once, rather than receiving one email every half hour or so.

3 answers

I have the same problem like John, someone know how to solve it ? 

0 votes

Hi John,

I am wondering if setting up plan build dependencies could help you. Can you please give it a try?

I hope this helps!

Kind regards,
Felipe Kraemer
Atlassian Support

I am facing the same issue, Had to go through the same approach (Calling bamboo via its rest API).
If I change the number of concurrent builds (Miscellaneous > Override default number of concurrent builds), my rest API call returns the following:

<status><status-code>400</status-code><message>Build requested but not started, you have reached the maximum number of concurrent builds allowed 1.</message></status>

Does anyone know a way to prevent it from happening? I would like to have the same solution as John Delaney described.


I know that I could have one stage only and one job and many tasks, but I'd at least like to know if there's a flag or something else easier to be implemented to avoid refactoring.


Yeah, you get mostly unuseful ideas instead of answers to your question :-/

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

179 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you