[
https://issues.jenkins-ci.org/browse/JENKINS-12581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158636#comment-158636
]
SCM/JIRA link daemon commented on JENKINS-12581:
------------------------------------------------
Code changed in jenkins
User: Michael Clarke
Path:
src/main/java/hudson/scm/CVSSCM.java
src/main/resources/hudson/scm/CVSSCM/config.jelly
http://jenkins-ci.org/commit/cvs-plugin/794afd76127191e6a5174647d0c2620f0aadd915
Log:
[FIXED JENKINS-753] Allows performing a clean checkout if update fails
[FIXED JENKINS-12595] CVS gets passed the module name so creates lock
files in the correct directory on the remote server
[FIXED JENKINS-12581] CVS plugin now forces a module name in the udpate
command to prevent an attempt to checkout all remote modules
> CVS: First CVS Update after Checkout reads whole CVS-Repository
> ---------------------------------------------------------------
>
> Key: JENKINS-12581
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12581
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Affects Versions: current
> Environment: Tomcat6 / RHEL5
> Reporter: chrisabit
> Assignee: Michael Clarke
> Priority: Blocker
>
> When migration from old CVS-Plugin to the new Jenkins CVS-Plugin "Local Name"
> isn't defined.
> This leads to a HUGE problem: The first CVS-Update (not the first
> CVS-Checkout! This works!) will execute:
> "cvs update -d -P -r HEAD -D 2012-01-30 16:37:56CE"
> Thus the whole CVS repository is read.
> Simple solution: When migrating: "Remote Name" and "Local Name" must both be
> set.
--
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
