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

Blue Ocean: When step failed, the last step also marked failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.117
      Pipeline latest versions at issue creation
      Blue Ocean 1.5.0
      Oracle Java 8u144
      SUSE Linux Enterprise Server 12 SP3
      Chromium 64
    • Similar Issues:

      Description

      In Blue Ocean the last step is always marked failed when a different step has failed.
      The step that actually failed is a few steps earlier.

      I have deleteDir() at the very last in try-catch-finally on every parallel build node. This on order to clean up. It says this step has failed, even though it has not.
      "Recursively delete the current directory from the workspace"
      Blue Ocean has this step marked as failed.

      It is always the last step that fails, in addition to the actually failed step.
      If I remove deleteDir() it is the previous step that now is marked as failed.

      The steps that are executed after the actual failed step is within a finally clause of try-catch.

        Attachments

          Issue Links

            Activity

            Hide
            djviking Sverre Moe added a comment -

            This issue might be ralted to JENKINS-46551.

            Show
            djviking Sverre Moe added a comment - This issue might be ralted to JENKINS-46551 .

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              djviking Sverre Moe
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: