|
||||||||
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)
Can you add the config.xml files from the 4 jobs, in particular the <publishers> ... </publishers> section.
And as the jobs are separate and there is no actual lick between them other than the upstream/downstream relationship there is no cause to prevent the jobs from running at the same time unless that advanced option is enabled.
See Advanced section in project A config and enable the block when downstream is building item and see if that fixes the problem.