[ 
https://issues.jenkins-ci.org/browse/JENKINS-12581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158514#comment-158514
 ] 

K P edited comment on JENKINS-12581 at 2/3/12 8:47 AM:
-------------------------------------------------------

I got similar issues. The behaviour was improved however when changing forward 
slashes in the ROOT and module into backslashes (tough I'm not using the CVS 
2.0 plugin anymore for now for other issues).
This was on a Windows system.

So you might try playing with the / or \ in the meantime, it did help me a 
little... until this is hopefully fixed and handled more nicely in the plugin.
                
      was (Author: belpk):
    I got similar issues. The behaviour was improved however when changes 
forward slashes in the ROOT and or module into backslashes (tough I'm not using 
the CVS 2.0 plugin anymore for now for other issues).
This was a Windows system.

So you might try playing with the / or \ or even \\ in the meantime... until 
this is hopefully fixed and handled more nicely in the plugin.
                  
> 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
>            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

        

Reply via email to