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

failFast option for parallel stages sets build status to ABORTED when failure is inside of a stage with an agent


    • pipeline-model-definition 1.3.7


      With a Pipeline using parallel stages with failFast true enabled, when a stage with an agent fails, the final build result is showing as ABORTED instead of FAILURE

      A similar bug was recently fixed JENKINS-55459 which corrected the build status result when using non-nested parallel stages with failFast true enabled, but it seems it did not catch the case where a nested stage inside of one of the parallel stages fails.


      The fix for JENKINS-55459 was delivered under version 1.3.5 of the Pipeline: Declarative Plugin, I am testing version 1.3.6.

      I started up a brand new Jenkins LTS 2.150.3 instance, with the 'recommended' plugins, including Pipeline: Declarative Plugin version 1.3.6

      I ran the testcase inside of JENKINS-55459 and the build status is correctly marked as failed, so the fix from JENKINS-55459 was correct.

      When I run the attached Jenkinsfile , the build still shows as ABORTED:

      ERROR: script returned exit code 1
      Finished: ABORTED

      Here is the full log: log

      I expected the build status to be marked as FAILURE, not ABORTED.


      I believe the fix from JENKINS-55459 worked, but does not account for failures inside of stages with agents within the parallel stages.

        1. Jenkinsfile
          2 kB
          Ray Kivisto
        2. log
          2 kB
          Ray Kivisto
        3. pipeline__Jenkins__and_Mozilla_Firefox.png
          100 kB
          Ray Kivisto
        4. test.png
          48 kB
          Ray Kivisto

            dnusbaum Devin Nusbaum
            rkivisto Ray Kivisto
            0 Vote for this issue
            6 Start watching this issue