Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16384

Blocking on downstream projects

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • join-plugin
    • None
    • Jenkins 1.480.1 LTS

      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).

          [JENKINS-16384] Blocking on downstream projects

          Alex Vesely created issue -
          ikedam made changes -
          Component/s Original: parameterized-trigger [ 15592 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 147202 ] New: JNJira + In-Review [ 176837 ]

            mdonohue mdonohue
            alex01ves Alex Vesely
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: