|
||||||||
|
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.
That's strange. After unchecking "Run on all nodes...," my original projects behaved correctly and no duplicate builds were generated. I didn't find this behavior stated in the NodeLabel Parameter plugin documentation. When would duplicate builds ever be intended? This doesn't explain why when I had upwards of 70 property files to use with the ParameterFactory, the triggered builds cascaded beyond just one extra build (the original problem was discovered by 3000+ builds in queue).
Also, I believe I had this setting checked from the beginning (I've got at least a 2-month, 40-build history through development), but only just last week observed this effect. Well, I can't explain it, but thank you all for the attention and help.
TL;DR (For others not expecting the behavior in the description) - If you are using a Property file ParameterFactory to trigger a child project with a node label parameter, if you check "Run on all nodes matching the label," you can expect multiple builds of the child project.