CVS update sometimes ignores changes

Hi,

i have a problem by using a cvs repository. Sometimes cvs changes are just not recognized by TeamCity. It happens to ~20% of all commits. I checked the cvs logs (DEBUG mode) but couldnt find any error.
Everything seems to be alright except of no changes reported! Example of Reply:

[2009-03-24 11:06:17,546]   INFO -      jetbrains.buildServer.VCS - Collecting changes for XXX; from version  2009/03/24 11:03:32 +0100; to version  2009/03/24 11:06:17 +0100; root=cvs-quiet-period=3
cvs-root=:pserver:user@server:/home/cvsroot
cvs-tag-mode=HEAD
history-supported=true
local-server-command=server
module-name=ro/xxx
secure:cvs-password=*****
ssh-port=22
ssh-use-ppk=false
teamcity:vcsRootName=XXX
vcs=cvs
[2009-03-24 11:06:17,546]  DEBUG -      jetbrains.buildServer.VCS - =>
[2009-03-24 11:06:17,546]  DEBUG -      jetbrains.buildServer.VCS - Stored change lists: 0
[2009-03-24 11:06:17,546]   INFO -      jetbrains.buildServer.VCS - CVS executing null
[2009-03-24 11:06:17,765]   INFO -      jetbrains.buildServer.VCS - CVS executing history -a -xAMR -p ro/xxx-D 2009/03/24 10:03:32 +0000
[2009-03-24 11:06:59,109]  DEBUG -      jetbrains.buildServer.VCS - Collected change lists: 0
[2009-03-24 11:06:59,109]  DEBUG -      jetbrains.buildServer.VCS - VCS plugin cvs reported changes for XXX; 0 changes collected
[2009-03-24 11:06:59,109]  DEBUG -      jetbrains.buildServer.VCS - cvs, set version: 2009/03/24 11:06:17 +0100 for project XXX
[2009-03-24 11:06:59,109]  DEBUG -      jetbrains.buildServer.VCS - Finish collecting changes for XXX; 0 changes collected 0 changes reported

Do anyone has an idea why this is happening?

Thanks,
Andi

Configuration:
Type:                                    CVS
Protocol:                               pserver
Quiet period:                          3
History command supported:   true
Checking interval:                   120s
Checkout mode:                     Auto Agent

13 comments
Comment actions Permalink

What version of TeamCity do you use?

0
Comment actions Permalink

Hi,

itsTeamCity Professional Version 4.0.2 (build 8222).

0
Comment actions Permalink

Is it possible that CVS repository history file is not updated properly? For example, user who makes a change does not have permissions to modify history file? Could you please check that changes not detected by TeamCity are properly recorded in the history file?

0
Comment actions Permalink

Hi,
changes of the same user sometimes goes threw sometimes not! In the cvs history (tortoiseCVS) everything is fine!
TeamCity sometimes just missing the changes. It is neither showing that a file was changed nor is it proceiding an update! On the filesystem TeamCity holds the old version then.
To solve that I have to delete the old file, so TeamCity is forced to get the up to date version, or procede a manual update threw TortoiseCVS.

Thanks,
Andi

0
Comment actions Permalink

In the log TeamCity shows commands issued by CVS plugin. Could you please do the following: try to reproduce the bug, then take a look at the TeamCity log and try to issue a command used by TeamCity. The command looks like:
cvs history -a -xAMR -p ro/xxx -D 2009/03/24 10:03:32 +0000

where ro/xxx is your module
and 2009/03/24 10:03:32 +0000 is a date before the change is made.

Please check that changes are shown by the command.

0
Comment actions Permalink

Hi,
thank you for your help!

I commited a file at 10:51. This commit didnt go threw. The DEBUG output was:
____________________________________________________________________________________________________________________________________
[2009-03-24 10:50:26,093]  DEBUG -      jetbrains.buildServer.VCS - cvs, set version: 2009/03/24 10:49:37 +0100 for project Frontend
...
[2009-03-24 10:52:27,546]   INFO -      jetbrains.buildServer.VCS - Collecting changes for xxx; from version  2009/03/24 10:49:37 +0100; to version  2009/03/24 10:52:27 +0100; root=cvs-quiet-period=3
...
[2009-03-24 10:52:27,546]  DEBUG -      jetbrains.buildServer.VCS - =>
[2009-03-24 10:52:27,546]  DEBUG -      jetbrains.buildServer.VCS - Stored change lists: 0
[2009-03-24 10:52:27,546]   INFO -      jetbrains.buildServer.VCS - CVS executing null
[2009-03-24 10:52:27,718]   INFO -      jetbrains.buildServer.VCS - CVS executing history -a -xAMR -p ro/xxx-D 2009/03/24 09:49:37 +0000
...
[2009-03-24 10:53:11,468]  DEBUG -      jetbrains.buildServer.VCS - VCS plugin cvs reported changes for Frontend; 0 changes collected
[2009-03-24 10:53:11,468]  DEBUG -      jetbrains.buildServer.VCS - cvs, set version: 2009/03/24 10:52:27 +0100 for project Frontend
[2009-03-24 10:53:11,468]  DEBUG -      jetbrains.buildServer.VCS - Finish collecting changes for Frontend; 0 changes collected 0 changes reported
____________________________________________________________________________________________________________________________________

Another commit (same user, same file, same computer,...) was 10:33. This commit went threw! DEBUG output:
____________________________________________________________________________________________________________________________________

[2009-03-24 10:34:07,750]  DEBUG -      jetbrains.buildServer.VCS - cvs, set version: 2009/03/24 10:29:54 +0100 for project xxx
[2009-03-24 10:34:10,609]   INFO -      jetbrains.buildServer.VCS - Collecting changes for xxx; from version  2009/03/24 10:29:54 +0100; to version  2009/03/24 10:34:10 +0100; root=cvs-quiet-period=3
...
[2009-03-24 10:34:12,171]   INFO -      jetbrains.buildServer.VCS - CVS executing history -a -xAMR -p ro/xxx-D 2009/03/24 09:29:54 +0000
...
[2009-03-24 10:35:08,406]  DEBUG -      jetbrains.buildServer.VCS - cvs, set version: 2009/03/24 10:29:54 +0100 for project xxx
[2009-03-24 10:35:11,265]   INFO -      jetbrains.buildServer.VCS - Collecting changes for xxx; from version  2009/03/24 10:29:54 +0100; to version  2009/03/24 10:35:11 +0100; root=cvs-quiet-period=3
[2009-03-24 10:35:11,265]  DEBUG -      jetbrains.buildServer.VCS - Stored change lists: 0
[2009-03-24 10:35:11,406]   INFO -      jetbrains.buildServer.VCS - CVS executing null
[2009-03-24 10:35:11,718]   INFO -      jetbrains.buildServer.VCS - CVS executing history -a -xAMR -p ro/xxx-D 2009/03/24 09:29:54 +0000
[2009-03-24 10:36:16,000]   INFO -      jetbrains.buildServer.VCS - CVS executing rlog
-N -S -d 2009/03/24 09:29:54 +0000<2009/03/24 09:35:11 +0000 -rHEAD -b ro/xxx/xxx/xxx/TheChangedFile.cs
[2009-03-24 10:36:16,203]  DEBUG -      jetbrains.buildServer.VCS - Date from server: 2009/03/24 09:33:37 parsed as 2009/03/24 10:33:37 +0100
[2009-03-24 10:36:16,218]  DEBUG -      jetbrains.buildServer.VCS - Collected change lists: 1
[2009-03-24 10:36:16,234]  DEBUG -      jetbrains.buildServer.VCS - VCS plugin cvs reported changes for xxx; 1 changes collected
[2009-03-24 10:36:16,234]  DEBUG -      jetbrains.buildServer.VCS - cvs, set version: 2009/03/24 10:35:11 +0100 for project xxx
[2009-03-24 10:36:16,265]  DEBUG -      jetbrains.buildServer.VCS - Finish collecting changes for xxx; 1 changes collected 1 changes reported
______________________________________________________________________________________________________________________________________

I dont know why, but in the second case Teamcity proceded twice. first time at: 10:34:10,609, second time at: 10:35:11,265 (trigger quiet period? it was set to 60sec)
Second time TeamCity found the change!

I dont know if its important, but im checking out 3 CVS modules. All of them are having this behaviour! I copied just the checkout where i tried to reproduce the error.

Thank you!!!
Andi

0
Comment actions Permalink

The problem can be in time synchronization between repository server and TeamCity server. Could you please ensure that time is synchronized and try again?

0
Comment actions Permalink

Hi,
the time of the TeamCity Server was ~20secs out of sync with the CVS Server! I configured on all Clients, the CVS Server and the TeamCity Server the same Time Server now! I will tell you if it works!

Thank you very much for your help!!!
Andi

0
Comment actions Permalink

We've a simular issue. The changes are not visible in TeamCity. However when a build is made the artifact does contain the update files!?!?
We encounter this issue since we've updating from 3.1.1 to 4.0.2

What should be done to resolve this issue?

Tnx in advance.

0
Comment actions Permalink

Please describe your settings: VCS root, checkout mode, checkout rules. Also please check that time is in sync on the TeamCity server and CVS repository server.

0
Comment actions Permalink

VCS root:
:pserver:wvb@lnx-web02:/home/cvs

Module:
OFS/webservice

Checkout rules:
.=>webservice

See attached image cvs-settings.PNG for all configuration settings.

The time between the build server and cvs repository server are synchronized.



Attachment(s):
cvs-settings.PNG
0
Comment actions Permalink

Could you please submit issue to our tracker: http://jetbrains.net/tracker
Please attach your VCS settings, checkout rules and so on. Also if you are using CVS modules file please attach it too.

0
Comment actions Permalink

Will do. Thanks for your help so far.

0

Please sign in to leave a comment.