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?
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.
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.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
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