Sources not updated on some agents (TC 6.0.3 build 15925 with TFS 2010)

Hi all,

we are experiencing a very annoying problem.

We are running the TeamCity server (6.0.3) on a Win 2003 R2 SP2 server, we are using server-side checkout and the TFS is the 2010 version.

Now we have this problem.

After a changeset A in a source code a build starts on agent01, and it works fine.

After a new changeset B a new build starts on agent02, but it fails because on this agent one of the file of the changset A was not updated.

If I clean sources on agent02 (without other changes) all works fine.

In the log of the build on the agent02 I see the message of the update of the folder containing the file more than one time. Is it right?

The file on the agent has the same modified date of the build, so it seems that has been changed, but not with the latest version

The file that was not updated correctly has changed 2 times since the last run on the agent02

[13:19:22]: Checking for changes
[13:19:38]: Clearing temporary directory: C:\BuildAgent\temp\buildTmp
[13:19:39]: Checkout directory: C:\BuildAgent\work\c2ddbebfcc2ffd08
[13:19:39]: Updating sources: server side checkout... (18s)
[13:19:38]: [Updating sources: server side checkout...] Building incremental patch for VCS root: GesDB
[13:19:56]: [Updating sources: server side checkout...] Repository sources transferred: 1.22Mb total
[13:19:56]: [Updating sources: server side checkout...] Updating C:\BuildAgent\work\c2ddbebfcc2ffd08\AprojectName01
[13:19:56]: [Updating sources: server side checkout...] Updating C:\BuildAgent\work\c2ddbebfcc2ffd08\AprojectName02
.....
[13:19:57]: [Updating sources: server side checkout...] Updating C:\BuildAgent\work\c2ddbebfcc2ffd08\AprojectName01
.....
[13:19:57]: [Updating sources: server side checkout...] Updating C:\BuildAgent\work\c2ddbebfcc2ffd08\AprojectName01

We have experienced this problem several times in the last weeks and it's very important for us to understand as soon as possible what is going wrong and if it's a bug or a problem in our environment.

Can anyone help us?

We have also the problem reported here:

http://devnet.jetbrains.net/message/5451296#5451296

I don't know if it's something related do this.

Any help would be appreciated.

Thanks

Andrea

Please sign in to leave a comment.