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
This question is in reference to Atlassian Documentation: Locating important directories and files
I am new to Bamboo cloud. And I just setup the remote agent in my build server. Somehow, I found it will automatically go offline aound 15 minutes. Did I miss anything or do anything wrong? My question is...
Thank you guys. I just figured out the problem by myself. Actually, what I need to do is just execute the command line "bamboo-agent-home/bin/bamboo-agent.sh start" to start the bamboo background process. Otherwise, the process will be stopped automatically if it is auto started by the installation.
Hope this also can helps others new to Bamboo.
I am facing the same issue where the bamboo remote agent goes offline after a specific interval resulting into job failures.
However, in my case, when I stop the services of 'Bamboo Remote Agent' from backend (services.msc), it is activated for a long time (during my working hours) and then it goes offline in my off time.
Could you please help with the steps to keep the remote agent always active?
Any help would be appreciated, I am so stuck right now.
Are you using your own remote agent or an Elastic Bamboo agent? If it's the latter, then it sounds like expected behavior as the default timeout for idle Elastic Bamboo EC2 instances is set at 10 minutes. This can be modified in the Elastic Bamboo configuration screen under Automatic elastic instance management.