|
||||||||
|
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 just ran the setup again with only one properties file and it built two child project jobs.
As for your second question, yes - I can't believe I didn't mention this before. The child project accepts a node label-type parameter. Just now, I found that without the node label parameter, this bug does not show up. If I remove the node label parameter from the child (but still pass it in the .properties file), no build duplication occurs. If I restore the node label parameter and manually build the child project, entering an existing node, no build duplication occurs.
If the parent project triggers a child project build using a .properties file (that contains an existing node label), build duplication DOES occur.
By the way, thank you both for paying attention to this issue.