[
https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159146#comment-159146
]
Fred G commented on JENKINS-12598:
----------------------------------
Hi,
I attached a UI mockup of a possible solution.
Every module configuration contains a radio group which lets the user choose
between
* a single module configuration (2.0 style) or
* a "module list" configuration that supports multiple modules (1.6 style).
The screenshot shows two module configs, one where the single module config
selected and one where the text area of the "module list" config is shown.
It should be possible to read out the text area and treat every entry as a
single module (without a local name) internally.
Please note: The overall layout of the CVS SCM config is far from perfect, but
once the functionality is there, it should be easy to adjust the graphical
representation.
@Ulli & @Michael What do you think?
> 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
>
>
> 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
