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

Bamboo Deployment Timeout

We have a situation where we invoke Ansible Playbook command from Bamboo Deployment and on rare occasions, it just waits on one of the steps in the playbook, forever. Since the Deployment never fails or succeed, we don't get notifications. Things get queued for that Deployment environment we don't notice until there's some error or failure in Production. 

It seems there's a timeout available for Build jobs that are based on the history of how long it takes to complete the plan. Is there something similar available for Deployment Environments? How can I potentially solve this problem?

1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 29, 2019

Hi @Subhi Andrews

I'll make some assumptions here:
    You are running the build in a Unix-like remote agent
    You are running the Ansible Playbook command from a script task.

Possible solution

  • Use the command timeout to define the maximum time you think the Ansible Playbook could take and still succeed.
  • Add the option set -e at the beginning of your script task. That will make the build fail for any command returning an error, including the result of timeout command when it kills a command after reaching the max time defined.


timeout -k 30 <TIME> <ANSIBLE_COMMAND>

In case of timeout, the command above will send to Ansible the SIGTERM and if the command stays running for 60s more, then it will send the SIGKILL.

I hope this helps.

We have added ansible-playbook as a capability and calling it has a command instead of a script. Is there a solution for that? Since we might have to make changes in many different jobs?

Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 30, 2019

Hi @Subhi Andrews

yes, you can use the Build monitoring feature, but that will consider the whole build time and will not work on local agents.

If you use remote agents that should work fine. =]

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events