Re: Jenkins CVS plugin does not detect changes

2012-03-26 Thread Spiff79
I've created issue JENKINS-13227 to track this. On Friday, March 23, 2012 2:42:04 PM UTC-4, Spiff79 wrote: > > The 4 hour difference corresponds to GMT-adjusted time, so it looks like > there's a mixup in time zones somewhere. Using CVS plugin 1.6 the cvs > polling command looked like this (exec

Re: Jenkins CVS plugin does not detect changes

2012-03-23 Thread Spiff79
The 4 hour difference corresponds to GMT-adjusted time, so it looks like there's a mixup in time zones somewhere. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D "Thursday, Ma

Re: Jenkins CVS plugin does not detect changes

2012-03-23 Thread Spiff79
I'm in the Eastern Time Zone (Montreal) with Daylight Saving Time in effect. The last cvs checkout command looked like this: cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt On Mar 23, 2:05 pm, Spiff79 wrote: > Even more details: Lo

Re: Jenkins CVS plugin does not detect changes

2012-03-23 Thread Spiff79
Even more details: Looking into the entries file, I'm seeing incorrect times for recently updated files, a 4-hour difference. Could this be related to the problem? On Mar 23, 1:49 pm, Spiff79 wrote: > More details: the previous CVS plugin version was 1.6 and it was using > the local cvsnt install

Re: Jenkins CVS plugin does not detect changes

2012-03-23 Thread Spiff79
More details: the previous CVS plugin version was 1.6 and it was using the local cvsnt install. On Mar 23, 12:04 pm, Spiff79 wrote: > Hi all, > > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. We've upgraded > the CVS

Jenkins CVS plugin does not detect changes

2012-03-23 Thread Spiff79
Hi all, We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. We've upgraded the CVS plugin to version 2.1 this morning and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of "cvs rlog"