-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
CentOS 6.3 Linux
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.
Code changed in jenkins
User: vimil
Path:
src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java
src/main/resources/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition/config.jelly
src/main/resources/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition/help-multiSelectDelimiter.html
http://jenkins-ci.org/commit/extended-choice-parameter-plugin/016e67f1ec4cb96db90264853392a3396b00d421
Log:
Merge pull request #2 from olhado/master
Added code for
JENKINS-17518Compare: https://github.com/jenkinsci/extended-choice-parameter-plugin/compare/444e5b894379...016e67f1ec4c