You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
We're seeing this on our internal bamboo instance with remote agents. Is there a corresponding issue/fix in bamboo 5.x ?
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 am having similar issues. They emanate in two ways:
|20-Sep-2019 19:22:20||Data Send took: 0.185|
|20-Sep-2019 19:23:51||Agent 'Elastic Agent on i-0495c84735905d1b6' went offline while building MH3DBBT-WRL-LBM01-13. The results of that build will not be available.|
2) Build triggered but not queued Reason for not building is unknown
This behavior is random. Any help is appreciated
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.