|
||||||||
|
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.
The more I think about it, the more I agree with you that we should stay away from macro/token/variable (anything with ${VARIABLE}), at least for now.
The problem is very simple: since a variable's evaluation may depend on data available only during the execution of the job, it's not possible to guess the possible values in a 'static' way while building the Label Dashboard. While it may still be doable albeit complex in some cases (Choice parameter), it will be impossible in other cases to determine programmatically the value of the variable without launching a build. Not reasonable.
In a nutshell: I will introduce a deliberate limitation in the plugin, and for now all labels (or strings considered as such) that contains ${} will be ignored.
Scenario 2: I will investigate in the code if it's feasible. If there is code in Jenkins that lets me easily access the list of predefined parameters and look for their 'type' in the triggered job, it could be added to the plugin.
Label parameter default value: I'll give it a try. It could be useful if a label is removed at some point, to easily find all jobs that were using it as a default value.
Last question, as I'm confused. You wrote above
so I'm asking what you mean by label description![]()
There'no place in Jenkins to enter a description when configuring a label. Or is there?