[JIRA] (JENKINS-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162803#comment-162803 ] James Gustafson commented on JENKINS-13264: --- Yes, it is Windows 7 64-bit with Jenkins 1.464 installed as a service. > fail checkout 2 modules with different path > --- > > Key: JENKINS-13264 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: linux >Reporter: Eric Co >Assignee: Michael Clarke > Fix For: current > > > I create two cvs modules with the path > lib/flac-1.2.1 > drv/linux/fuse > when it check out, got the error: > cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 > lib/flac-1.2.1 > cvs [checkout aborted]: could not change directory to requested checkout > directory `lib': No such file or directory -- 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-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162777#comment-162777 ] James Gustafson commented on JENKINS-13264: --- With the 2.4-SNAPSHOT, I find a need to use a back-slash for the "Local Name", then it works. For example: Remote Name: lib/something Local Name: lib\something It properly puts the checkout to workspace/project/lib/something. If I set "Local Name" to be lib/something, I get that same error 'No such file or directory'... My build server is Windows 7 with the cygpath plug-in if that matters. Anyway, it is working for me this way. Thanks Michael. > fail checkout 2 modules with different path > --- > > Key: JENKINS-13264 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: linux >Reporter: Eric Co >Assignee: Michael Clarke > Fix For: current > > > I create two cvs modules with the path > lib/flac-1.2.1 > drv/linux/fuse > when it check out, got the error: > cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 > lib/flac-1.2.1 > cvs [checkout aborted]: could not change directory to requested checkout > directory `lib': No such file or directory -- 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-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=162300#comment-162300 ] James Gustafson commented on JENKINS-13227: --- I have the same problem, CVS Plugin 2.3 doesn't detect changes on a branch for me, but works on the HEAD, as previously mentioned. If there is any more information I can provide please let me know. Using 1.462 with the 2.3 CVS Plugin. My backup machine works fine using CVS Plugin 1.6 with the same settings. > 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 > > 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-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162299#comment-162299 ] James Gustafson commented on JENKINS-13264: --- Can such an option be added? What would the difference be from what the "Legacy mode" option is supposed to do? I have the same issue as the OP except with one module with a bunch of legacy directories. The "Legacy mode" doesn't work with the 2.x CVS plug-in. And I get the same error as the OP if I try to set the "Local Name" to the same path as the "Remote Name". Thanks. > fail checkout 2 modules with different path > --- > > Key: JENKINS-13264 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: linux >Reporter: Eric Co > > I create two cvs modules with the path > lib/flac-1.2.1 > drv/linux/fuse > when it check out, got the error: > cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 > lib/flac-1.2.1 > cvs [checkout aborted]: could not change directory to requested checkout > directory `lib': No such file or directory -- 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
