[
https://issues.jenkins-ci.org/browse/JENKINS-12862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Clarke closed JENKINS-12862.
------------------------------------
Assignee: Michael Clarke
Resolution: Duplicate
Duplicates JENKINS-12581
> CVS confused about what to checkout and where to checkout to
> ------------------------------------------------------------
>
> Key: JENKINS-12862
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12862
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Affects Versions: current
> Reporter: nhnb
> Assignee: Michael Clarke
> Priority: Critical
>
> The recent CVS plugin is confused about what to checkout and where:
> CVSROOT: :pserver:anonym...@arianne.cvs.sourceforge.net:/cvsroot/arianne
> Remote Name: stendhal
> This configuration used to work in the past. But now it does a checkout of
> every module in the CVS-repository and it places this checkout above the
> workspace folder. As a result, the CVS changes are invisible because the last
> checkout below the workspace folder remains unchanged.
> Using different configurations of the Localname (empty or non empty) and
> Legacy Mode checkbox may result in only the right module to be checked out,
> but not into the workspace folder but a subfolder with the module name below
> the workspace folder. Again, this will result in the checkout being mostly
> invisible because an outdated version remains at the correct location.
> Furthermore deselecting the legacy mode checkbox is ignored. After saving the
> form and reopening the configuration form, the checkbox is selected again. It
> is possible to deselect it directly in config.xml, but this just causes the
> CVS plugin to again do a checkout of all modules to the parent folder of
> workspace.
> I tried several combinations of the configuration settings but I am still
> unable to find a workaround for this issue.
> Out jenkins server is publically available at
> http://stendhalgame.org/jenkins/job/stendhal_HEAD
--
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
