Issue Type: Improvement Improvement
Affects Versions: current
Assignee: Unassigned
Components: extended-choice-parameter
Created: 08/Apr/13 3:18 PM
Description:

Currently the multiselect choice parameter delimits multiple selections with a comma.

I have a situation where I am trying to create a staging/release package from multiple archived builds for use in an automated deployment system. I would like to use the multiselect choice parameter to select locations that the packages are going to be deployed to, and create a path structure with that information.

As I do not want to necessarily create deeply nested folders, it would be nice to either declare the delimiter myself or choose from a small set of directory name safe characters (windows or linux).

I think the comma delimiter should clearly be the default behavior.

Environment: CentOS 6.3 Linux
Project: Jenkins
Priority: Major Major
Reporter: Michael Chmielewski
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to