![]() |
|
|
|
|
|
|
Change By:
|
ikedam
(23/Mar/14 3:19 AM)
|
|
Summary:
|
Extend name pattern to use dots too
Check variable names as Jenkins core expands
|
|
Issue Type:
|
Task
Improvement
|
|
Assignee:
|
ikedam
|
|
Priority:
|
Minor
Major
|
|
Description:
|
After the parameterized trigger plugin wants to exchange all choices to extensible choices we have to change many properties in our jobs. But that's OK.
Problem:
Because of many of our properties containing dots we have to overwork half of our build process.
Suggestion:
Please check if the name of a property can contain . too.
----
Extensible Choice Parameter checks parameter names as Jenkins 1.466 expands variable
(that is, alphabets, numbers, and underscore: https://github.com/jenkinsci/jenkins/blob/jenkins-1.466/core/src/main/java/hudson/Util.java#L111 )
Jenkins 1.526 gets to allow dots in JENKINS-16660, [f664639|https://github.com/jenkinsci/jenkins/commit/f664639b79d2dea2abdf48816b01f8ccc525a73f].
Extensible Choice Parameter should check parameter names as the Jenkins core it runs on.
|
|
|
|
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/d/optout.
I decided how to do.
Target version is 1.3.0.