Is there any way to programmatically shut down a Bamboo remote agent after successful job execution to make sure it is not reused for another pending build job in the queue?
Problem we have ATM is that sometimes when running integration tests against Confluence, there are some Java processes hanging after tear down. This will make subsequent build tasks processed by this remote agent to fail.
Thanks for your help!
1 Like
AFAIK you cannot communicate directly with a Bamboo remote agent, so if you want to do this you will have to create a separate agent on that machine that listens to a command (which you can trigger from the Bamboo server). Feels a bit like a stretch though, maybe it’s better to tackle the original problem?
1 Like