[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163376#comment-163376 ] James Gustafson commented on JENKINS-13227: --- Using the latest 2.4 snapshot from May 31, Jenkins is now able to detect changes for me, and it fixed the "No file version found for the specified tag" issue that I started seeing as well. I am back to making regular builds, thanks for the fixes! > 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
[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163282#comment-163282
]
James Gustafson commented on JENKINS-13814:
---
The fixes in the latest 2.4 Snapshot work for my build now. Thanks a lot!
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
>Assignee: Michael Clarke
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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
[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log
James Gustafson created JENKINS-13814:
-
Summary: java.lang.OutOfMemoryError exception when getting the
remote log
Key: JENKINS-13814
URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
2.4-SNAPSHOT
Reporter: James Gustafson
We are getting a java.lang.OutOfMemoryError exception when getting the remote
log.
{quote}
Started by an SCM change
Building in workspace C:\x\workspace\project_name_here
cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d path\projects
path/projects
cvs checkout: Updating path\projects
cvs checkout: Updating path\projects/dir1
cvs checkout: Updating path\projects/dir2/dirA
... (about 7,224 directories) ...
cvs checkout: Updating path\projects/dirN
cvs rlog: Logging path\projects
... (about 7,224 directories) ...
cvs rlog: Logging path\projects/dirN
FATAL: Java heap space
java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
at java.lang.StringCoding.decode(Unknown Source)
at java.lang.StringCoding.decode(Unknown Source)
at java.lang.String.(Unknown Source)
at java.io.ByteArrayOutputStream.toString(Unknown Source)
at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
{quote}
Some notes:
- The path/ and path\ comes from the "Remote Name"/"Local Name" settings
solution from Issue JENKINS-13264
- We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
but may not have been caused by this specific version
- The arguments setting in the jenkins.xml file currently has -Xms1024m
(anything larger and Jenkins service won't start)
- The CVS module has many legacy projects spread out, and thus, contains more
than 7,000 directories and many more files
- Things had worked with the 1.6 plug-in & CVSNT client, but it also
occasionally timed out getting the changelog, hence our testing of the 2.x
plug-ins
--
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
