|
||||||||
|
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.
I just experienced/noticed this issue in 1.570. I have an upstream project that was choked out for an extended period of time while downstream builds that are configured to be blocked by the upstream built anyway. The downstream builds entered the queue after the parent, but they built first. Additional, new downstream builds compounded the problem until checkins in those builds quieted down. In some cases, three builds of children that should have built after the parent built before they should have according to "Block build when upstream project is building" rules.