What's being built is not matching what was tagged.

Here's the problem: we have a developer whose changes are not going into the cvs history file for some reason, so TeamCity is not detecting them.  We'll work on fixing that.  But here's the strange part:

At 3pm yesterday, he checked in a change did not compile.  At 7pm, I started a build, and the build compiled.  It should not have.  If his change had been in there, the compile would have failed.  And, when that build finished, TeamCity tagged CVS, with the tag b_605.  I checked out a working directory at tag b_605 and tried to build, and the compile failed.  So TeamCity included his broken change in the tag, but that was not (apparently) what was built.

What's going on?  How could TeamCity be building a set of sources that doesn't include changes checked in hours ago, and how could the tag not match the sources which were actually built?

3 comments
Comment actions Permalink

And now, what is really strange, is that since yesterday afternoon, the TeamCity compile has been failing.  Because it now apparently picked up the change checked in Thursday which broke the build, but has not yet picked up the change that fixed the build, checked in Friday morning.  Despite the fact that it has already included changes checked in later on Friday.  Even now, Saturday, a day later, the TeamCity compile is still failing because it is still missing that Friday morning checkin.  I've double checked that if I check the latest sources out locally, they compile fine.

Does TeamCity cherrypick each change it includes in a build, rather than just taking all changes at a particular point in time?  And if so, that seems to be inconsistent with the way it tags the VCS, which seems to tag based on a time.

0
Comment actions Permalink

Could you please check that time on TeamCity server and on the server where your repository is installed is in sync. If so please submit a bug report and attach there logs from the server and detailed description of the configuration where this error occurs: VCS roots, checkout rules, checkout mode (on agent or on server).

0
Comment actions Permalink

Opened http://www.jetbrains.net/tracker/issue/TW-7292

The ticket includes our configuration and log files.

It does not appear to be a time sync issue.  We have already encountered and fixed that problem a while ago.  Both the TeamCity server and the CVS server NTP to the same time servers now.

0

Please sign in to leave a comment.