[
https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158603#comment-158603
]
G. Ann Campbell commented on JENKINS-12598:
-------------------------------------------
Fortunately I only bit on this upgrade on my test server. I came back a couple
days later to find my disk usage at 100%.
On further investigation, I found every job had checked out the entire
respository into project root. Not workspace, but ../workspace.
When I checked the configs of some of the jobs, it showed that "Head" was
selected for each one. I'm still not quite sure what went wrong, but I've gone
back to v1.6
> In 2.0 update you need to specify branch for every module
> ---------------------------------------------------------
>
> Key: JENKINS-12598
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12598
> Project: Jenkins
> Issue Type: Improvement
> Components: cvs
> Reporter: Ulli Hafner
> Assignee: Michael Clarke
> Priority: Critical
>
> After an upgrade to the new 2.0 version of the cvs plug-in we now need to
> specify the "Module location" (trunk, branch) for each module. This is quite
> cumbersome if you have a lot of modules. In the 1.x plug-in releases you are
> able to select a given branch for all modules in one text field.
> While I think the new "feature" has a lot of use cases (i.e., having trunk
> and branches mixed), the usability could be improved here. My requirement is
> to select/change the branch (or trunk) for all modules in a simple way.
> A non-Ajax suggestion would be to have a "default" entry in the Selection,
> i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at
> the top of the cvs configuration.
--
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
