Cloned build agents & VCS checkout mode "Automatically on Server"

Hi,

We have recently made the leap from one buildagent to two buildagents. This was done by cloning the original buildagent & then changing its name.

Our buildconfig uses VCS checkout mode "Automatically on Server". Recently we have found a few cases where builds are running without the latest source. It seems like TeamCity is losing track of which source patches it has sent to which buildagent. The TeamCity server seems to send a particular patch to the first buildagent, and then behave as if it had sent that patch to both buildagents.

Can anyone tell me how the TeamCity server keeps track of which patch has been sent to which buildagent? Would the fact that we cloned the original buildagent be the cause of this issue? If so, how can we fix it?

We are (still) using TeamCity 5.0.2

Thanks,

Darren.

3 comments
Comment actions Permalink

Not sure if it helps, but if there is authorizationToken property in buildAgent.properties files for these agents and it has the same value? If so I would try to change it for one of the agents.

0
Comment actions Permalink

Hi Pavel,

Thanks for the answer. I've checked, and the build agents do have a unique authorizationToken properties in their buildAgent.properties files

Grasping at straws, I did delete all of the work directories on each build agent. TeamCity has re-created them, and we haven't seen the faulty VCS behaviour since (so far).

Darren.

0
Comment actions Permalink

We have the same issue I believe, that I have reported in thread: http://devnet.jetbrains.net/thread/434337?tstart=0.

Would be really nice to know a better workaround than deleting all build agent directories. We have read-only access to those folders on the build agent servers so it's not practical.

It seems we've found workarounds before but we're not sure exactly. We think maybe by recreating the VCS Root and attaching the new one to the build. I will try that if I have access to do it.

0

Please sign in to leave a comment.