[
https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161343#comment-161343
]
Fred G commented on JENKINS-12598:
----------------------------------
I agree, my mockup is definitely not the best.
Nevertheless I think there is a need for a text field that allows a large
number of modules to be pasted in.
That's also what Ulli requested in the issue's description.
As mentioned on IRC, when a large number of modules is checked out, it's pretty
save to assume that no custom local names are used. Therefore no local name
field is needed in that case.
If a user wants to use local names anyways he can still specify them as single
modules.
> 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
> Priority: Critical
> Attachments: Jenkins_CvsPluginModules.png,
> repositoryLocationProposal.png
>
>
> 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
