[
https://issues.jenkins-ci.org/browse/JENKINS-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158836#comment-158836
]
A Geller edited comment on JENKINS-12586 at 2/9/12 9:56 PM:
------------------------------------------------------------
I'd like to point out, that this issue affects me as well. Jenkins initiates
plenty of cvs requests. Unfortunately the number of cvs processes increases
steadily, resulting in a non-responding Jenkins server.
Env.: Jenkins 1.450 & CVS Plugin 2.0
The latter point has been mentioned in #JENKINS-12612
was (Author: agel07):
I'd like to point out, that this issue affects me as well. Jenkins
initiates plenty of cvs requests. Unfortunately the number of cvs processes
increases steadily, resulting in a non-responding Jenkins server.
Env.: Jenkins 1.450 & CVS Plugin 2.0
> cvs-plugin fails to read old changelog files
> --------------------------------------------
>
> Key: JENKINS-12586
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12586
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Affects Versions: current
> Environment: jenkins 1.449, cvs-plugin 2.0
> Reporter: Alex Lehmann
> Priority: Minor
>
> after updating to cvs-plugin 2.0, I get an exception when parsing the old
> changelog files that were written by the previous version of the plugin, e.g.
> Caused by: java.text.ParseException: Unparseable date: "2011-12-14"
> at java.text.DateFormat.parse(DateFormat.java:337)
> at
> hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:232)
> ... 34 more
> the corresponding changelog entry looks like this
> <changelog>
> <entry>
> <date>2011-12-14</date>
> <time>23:26</time>
--
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
