I have set up an on demand build plan, with an elastic agent that starts up on demand when the bamboo build queue, using passive instance managment. I have run 3 builds and 2 of them have have failed with the error
[MY BUILD NAME]: Agent 'Elastic Agent on i-52e8c135' went offline while building JOB-12. The build results will not be saved.
I cant see any logs.
The agent should stay online until the build has finised and the idle time has passed, but it seem to just shut down randomly. How can I fix this?
I am getting this as well. I just set up a Windows AMI for Bamboo AOD 4.1 and it randomly goes offline
Agent 'Elastic Agent on i-e8ace290' went offline while building TC-TESTS-WINDOWSSERVER2008R264BITCONFIGURATION-211. The build results did not finish.
How can I debug this and work out why my AMI is bombing out? Sometimes it works fine... :(
Here's the log file:
I think the cause of this was very long builds, as our maven build was having to download the repository from scratch each time. I fixed this by adding EBS with a pre loaded maven repo, and setting up a Nexus repository running in the cloud , and pointing the settings.xml in the EBs to point at this repo, so that any extra artifacts needed can be downloaded quickly.
Our builds are running very fast and with no problems now.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot