|
||||||||
|
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.
Scenario 1: yes this looks like the TokenMacro plugin usage. I will look deeper in this scenario, maybe I can still cover it in my plugin. I've never used the tokenmacro plugin, how and where do you define the MAP_LABEL variable?
Scenario 2: I didn't bother about Predefined parameters, because documentation of NodeLabel Parameter says that "it is not possible to use the 'Predefined parameters' to overwrite such a parameter, therefore the NodeLabel Parameter plugin adds a new parameter to the trigger plugin.". I guess that's not completely true![]()
So in your screenshot, 2hLoop is a label defined on your node(s), correct? And the string NODE corresponds to what? To a parameter defined in the triggered job? Looks fairly complex: does it mean that I need to check the definition of the triggered job (2h_Parts in your example), scan its list of parameters, and see if there is one called exactly NODE and if it's of type node/label (= using the NodeLabel Parameter plugin)?
What do you call label description?