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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Add wait time between concurrent builds

Hello there,

I would like to understand if it is possible to add wait time between concurrent builds please.

Basically I have a Bamboo plan with three agents dedicated to the plan and the concurrent build is set to 3.

Let say a build is executing on one agent, the build on the next agent should start after X mins of the first build and likewise the build on three agent should initiate after the X mins of second build.

Let me know if my statement is not clear.


Thank you!

1 answer

1 vote
Eduardo Alvarenga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 15, 2021

Hello @Rajib Dey,

Welcome to Atlassian Community!

There is no such feature in Bamboo. You can work around that by using a script task that will put a delay on the initial job execution.

You will need a common filesystem mounted on all Bamboo agents. This is mandatory so they can communicate and decide on the job execution order.

The following script needs to run as the first task in a Job. It will check if the control file exists, if so it will ask for a file lock. Make sure your NFS/CIFS/Clustered filesystem implementation allows file locking.

If a lock is granted, then it will proceed with some extra checking that will decide if it needs further sleep for X amount of seconds before exiting, but only if the current control file timestamp is lower than the sleep time.

# time in seconds
# this file should be in a NFS/CIFS share where all agents can write to
curr_time=$(date +%s)

if [ ! -f ${control_file} ] ; then
touch ${control_file}
control_file_time=$(stat --format=%Y ${control_file})
exec 100>${control_file}.lock
if flock 100; then
sleep_time=$(( $curr_time - $control_file_time ))
if [ $sleep_time -lt ${wait_time} ]; then
sleep $(( ${wait_time} - ${sleep_time} ))
echo "Run at second: $(date +%S.%N)"
touch ${control_file}

This is just an example which you can adapt to your needs. It will work in Linux, in Windows you can use PowerShell to achieve similar behaviour.



Eduardo Alvarenga
Atlassian Support APAC

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events