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.
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
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