Cloud agents not starting automatically
Hello
We recently upgraded our TeamCity server (version currently shows to be TeamCity Enterprise 2017.1.1 (build 46654)). We have a couple of cloud agent pools for EC2 build agents to be launched when builds are needed. These used to work fine (launch when needed, shut down after the idle time has passed) but since the upgrade they dont seem to start automatically anymore. If I go to Agents - Cloud, the pools are listed there. If I click on the Start button for one of the pools, it launches and agent, then launches a few more, builds run, and then eventually they shut down. It seems the launch trigger is not working. I don't see any errors in Administration - Diagnostics - Server Logs - teamcity-clouds.log, nothing is logged there when builds are queued, but no cloud agents are launched. Any ideas why this is happening, or what else I can check?
Please sign in to leave a comment.
For reference for anybody that might come across this issue and find this thread, we discussed this issue through our internal support. After an upgrade to 2017.1, new cloud agents might need to be manually started a first time before they get automatically started for builds. It might also take some time for them to be started automatically.
In 2017.1 TC, can we still create an agent cloud profile cross all root projects? If no, we will have to create agent cloud for each root project, it's not convenient for us. If yes, can we create agent pool for all root projects?
Hi Jack,
sorry for the delay, the message got lost in my inbox and I just retrieved it. Yes, you can create a profile in the root project and all inherited projects will be able to use that profile's agents.