|
||||||||
|
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.
After re-creating a parent-child project configuration with new projects, I've found that as soon as I add slave creation (and deletion at the end) and trigger builds to run on the label given to them, I can reproduce this issue. I will continue to hone in on my configuration of projects to see where the issue may reside. Intuitively, the creation of Jenkins slaves should have no correlation to the trigger build step that causes the runaway ChildProject builds, but the runaway happens explicitly when slave creation is added.
I apologize for my shotgun approach earlier.
Additionally, do you have any idea when the next release will happen? I know that FileBuildParameterFactory logging would be of paramount use here.