|
||||||||
|
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 ageee @danielbeck.
This is a configuration issue.
It's not a bug, but a feature (or a limitaion) of Jenkins core.
Anyway there's nothing parameterized-trigger can do.
I'll close this issue with Not A Defect.
Before that, I'll see the bahavior of Jenkins for labels same to existing node names (for example, whether displays warnings for those labels), and a new issue for Jenkins core.
I believe notices for that problem should have been written in the help text.
https://github.com/jenkinsci/jenkins/blob/jenkins-1.584/core/src/main/resources/hudson/model/Node/help-labelString.html