|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... [email protected] (JIRA)

Do you mean if job E has 'block if upstream is building' enabled? No, it has both the 'block' flags unchecked.
Can the issue be connected to the "Check job prerequisites" script that job E runs before finding a good slave for execution?