Team City Cloud Agent Slow starting
Hey Guys,
We are using the Kubernetes plugin to start cloud agents in Open Shift. This works absolutely fine but we are experiencing issues with agent start up times.
This has been investigated and every time we start a new agent the server initiates an update to the plugins which isn't desirable,
We have tried various different ways to get around this, like copying the plugins to the correct location on the agent image but the server ultimately issues an upgrade request
Note:
The agent is the same version as the server.
The agent starts up and finds the plugins and then initializes them, then the server issues an upgrade request and the process starts again i.e copies the plugins across and starts initialization again.
We need to find a way of stopping this automatic update process otherwise our builds are to slow to use cloud agents.
Any ideas?
Please sign in to leave a comment.
Hi Jon,
If you start the agents manually (start an image from the cluster manually and let the agent connect), does it do the same? If it's the case, it would make sense to have the agent pull the upgrade, let it finish the process, then take the image with the new state. That should prevent the agents from being restarted to pull the info. Tampering with the contents of the folders will end up in teamcity assuming that it needs to pull the plugins again.
Once you try this, if it keeps happening, please start up an agent with the new image, let the upgrade process go through, then collect teamcity-server.log, teamcity-agent.log and upgrade.log, the last two from the agent and forward them to us using the "Submit a request" button above.