What triggers an agent upgrade?

We have ec2 agents configured and it has the latest of everything on the image.  When the ec2 instance starts up it is always saying upgrading agent.  Is there a way to tell why the agent needs to be upgraded?  Is this avoidable?  How is the teamcity server deciding it needs an upgrade?  Is this something that always happens if the agent was never registered?

Thanks,
Jay

4 comments
Comment actions Permalink

When agent connects to the server, it sends information about own plugins to the server, and server initiates agent upgrade if agent lacks some of the plugins or tools. Note that build agent installer bundled with TeamCity does not have any plugins, so it has to be upgraded. Server also initiates upgrade if agent version does not match server version (i.e. server was recently upgraded, or downgraded).

0
Comment actions Permalink

Is there any method to keep the agent from building jobs until that initial upgrade is complete? We have the issue where the plugins need to be installed, but it has already started it's first build and then ends up cancelling it.

0
Comment actions Permalink

I'm running into a similar issue where I've installed the TeamCity build agent, ran through a few builds, cleaned up the temp/log directories, and then created a new AMI in AWS.

When I spin up Spot or On-Demand instances based upon the AMI the agent always upgrades itself which takes around 2 minutes even though it already has all of the latest plugins and tools.  In the upgrade.log it doesn't pinpoint why it is upgrading itself.

Anyone have any guidance on where to look to figure out why the agent is updating itself?

I'm following this documentation - https://confluence.jetbrains.com/display/TCD10/Setting+Up+TeamCity+for+Amazon+EC2#SettingUpTeamCityforAmazonEC2-PreparingImagewithInstalledTeamCityAgent

0

Please sign in to leave a comment.