|
||||||||
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 |
- [JIRA] (JENKINS-16384) Blocking on downstream p... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
I have managed to reproduce what I think is the issue.
and the steps are
Trigger A1
A1 triggers B1
Other Jobs triggers E1
Trigger A2
B1 triggers C1, D1
C1, D1 trigger E2
E1 runs
A2 runs
E2 waits until B2,C2,D2 have finished.
In this case I have enabled the Block when upstream is building on project E.
and seem to see the same issue as JENKINS-14918
Where E2 is seen as Blocked because E1 is building
The the queue is processed in order with A2 checked first and E2 is still classed as blocked so A2 is run.
Then E2 is checked and still blocked due A2 running.
Can you check the settings for Job E and see if this is the case.