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

job triggered by join didn't wait for all downstream jobs to finish

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • join-plugin, parameterized-trigger-plugin
    • None
    • Hudson v1.377, Win Server 2003 R2 x64 SP2, Join v1.9, Parametrized trigger v2.7

      Hudson v1.377
      Join plugin v1.9
      Parametrized trigger v2.7

      Job A calls job B, C, D and E via the parametrized trigger. The join in job A should start job F when all are stable. However, F started after B, C and E finished while D was still waiting for a free slave.

      The parametrized trigger of B, C, D and E is called from within the join by setting the post actions.

      On a side note the jobs C and D starting each another 2 jobs via parametrized triggers.

        1. join.png
          join.png
          11 kB

            mdonohue mdonohue
            robsimon robsimon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: