[
https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162531#comment-162531
]
Michael Clarke commented on JENKINS-13227:
------------------------------------------
Yes and No. The modified plugin seems to pick up changes but then hangs after
parsing some of them. I've not been able to narrow down what's causing this but
I suspect it's a dodgy regular expression resulting in a field matching
repeatedly and therefore going into a loop. I'll upload my changes as soon as
I've fixed this issue so that you can try them.
> CVS plugin 2.1 does not detect changes
> --------------------------------------
>
> Key: JENKINS-13227
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13227
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Reporter: Guillaume Bilodeau
> Assignee: Michael Clarke
> Priority: Critical
> Labels: cvs
> Attachments: rlog.txt
>
>
> As presented in the user group:
> https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4
> 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. The CVS plugin (v1.6)
> was using the local cvsnt install.
> We've since upgraded the CVS plugin to version 2.1 (by manually pinning the
> plugin) and since then, CVS changes are not detected. The CVS polling log is
> triggered properly, tons of "cvs rlog" instructions are sent, but at the end
> "No changes" is displayed.
> 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, March 22, 2012 9:26:21 PM UTC"
> Using CVS plugin 2.1, the last cvs checkout command looked like this
> (executed at 11:56:16 AM EDT):
> cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012
> 11:56:16 EDT -d portailInt portailInt
> We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
