[JIRA] [extensible-choice-parameter] (JENKINS-22222) Extend name pattern to use dots too

[de...@ikedam.jp (JIRA)]

ikedam commented on JENKINS-22222 Extend name pattern to use dots too It depends on how to use it. If used in shell or windows batch, it would does not work correct. Current parameter name check is performed under the rule of bash (alphabets, numbers, underscore). Though I haven't tested yet, it would work correct in almost other cases even the configuration page displays an error. Groovy scripts would also work well as they access build variables as a map object. I'll ask Jenkins developers whether there is a guideline about parameter names, and consider what's the best way. For now, I think followings are good for your case. Test parameters with dots work correct in your environments. Error messages in configuration pages are just informational, and Extensible Choice Parameter does not kick those values even in future releases. But I cannot ensure Jenkins itself accepts any values even in future reases... I still recommend you to use bash-like parameter names if you can easily adapt it. There may be a day you want to access those values from bash scripts or windows batches.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.