TeamCity 3.1.2 upgrade issue - build agents become disabled


I upgraded TeamCity 3.1.1 to 3.1.2 today. The upgrade went fine.

I have one minor issue with the upgrade process that I believe happened in the previous upgrade (3.1 to 3.1.1):
if you have more than one build agent, build agents other than the default build agent are disabled after the
upgrade. I had forgotten about this and it took me several minutes to realize why my 2nd build agent was
not available.

Suggestion: either document the fact that this will happen as part of the upgrade process or have the upgrade
process recreate the state of all build agents before the upgrade.


Comment actions Permalink


Agents should never change their disabled/enabled state without direct user action. What I believe you experienced was that agents become unauthorized.

Actually, agents should preserve their authorization state on upgrade. There are several limitations, though:
- agent's IP, port and name should not be changed.

If any of this change, you can get unauthorized agent with appropriate message on the agent's details page about when and why it was unauthorized.

Can this be the case in your environment? Do you have DHCP-assigned IP addresses or several agents running on thew same machine with no unique "ownPort" setting in the

Anyway, in 4.0 we are maintaining agent authorization by a special token and not their IP, so all types of these issues should be gone with 4.0.

Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
"Develop with pleasure!"

Comment actions Permalink

I am glad this is fixed in 4.0. It is minor and easily fixable. But it took me a bit of time to figure out why this build agent (which runs the majority of my builds) was not working.

To answer your question: Nothing has changed on the build agent that was disabled after upgrading from 3.1.1 to 3.1.2.

Here is a bit about my configuration:
TC Server & default build agent: Red Hat Enterprise Linux ES release 4 (Nahant Update 4)
2nd build agent (the one that was disabled): Windows XP Pro SP2



Please sign in to leave a comment.