Issue Type: Bug Bug
Assignee: mdonohue
Components: join, parameterized-trigger
Created: 17/Jan/13 6:03 AM
Description:

My job dependency graph looks like this:

A starts B. B starts C and D and 'joins' with E.

Expected behavior: [assuming everything runs successfully] A should never start before E has completed.
Reality: sometimes it does. And as it performs clean-up of some common folders, this messes up E completely.

Potentially relevant info:

  • E can be run as a 'join' job from other job flows, not just A-B-C-D.
  • All triggering is performed via "Trigger parameterized builds" (I'm including the parameterized-trigger component to the report as well).
Environment: Jenkins 1.480.1 LTS
Project: Jenkins
Priority: Critical Critical
Reporter: Alex Vesely
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

Reply via email to