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

unsuccessful block is triggered for successful runs

    XMLWordPrintable

Details

    • pipeline-model-definition 1.3.5

    Description

      The post-unsuccessful block of my declarative pipeline is triggered even if the build is successful!

      Excerpt from my Jenkinsfile

      pipeline {
  stages { ... }
  post { 
    always { ... }
    success { ... }
    unsuccessful {
      script {
        echo "Build results: ${currentBuild.result} - ${currentBuild.currentResult}"
        ...
      }
    }
  }
}

      And I can see `Build results: SUCCESS - SUCCESS` in the pipeline output - and the other steps of the unsuccessful block executed as well, of course

        

       

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-55265 Unsuccessful post stage fires even on Success status

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-49997 Pipeline Declarative post unsuccessful block

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link jenkinsci/pipeline-model-definition-plugin#313

          Activity

            Ascending order - Click to sort in descending order
            dnusbaum Devin Nusbaum added a comment -

            I noticed this as well in https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/313, (the main point of that PR is not related, I just happened to see it) and added a fix for it there. See https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/313#discussion_r259517064 specifically.

            dnusbaum Devin Nusbaum added a comment - I noticed this as well in https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/313 , (the main point of that PR is not related, I just happened to see it) and added a fix for it there. See https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/313#discussion_r259517064 specifically.
            dnusbaum Devin Nusbaum added a comment -

            The fix for this issue was released in version 1.3.5 of the Pipeline: Declarative Plugin.

            dnusbaum Devin Nusbaum added a comment - The fix for this issue was released in version 1.3.5 of the Pipeline: Declarative Plugin.
            bitwiseman Liam Newman added a comment -

            Bulk closing resolved issues.

            bitwiseman Liam Newman added a comment - Bulk closing resolved issues.

            People

              dnusbaum Devin Nusbaum
              kutzi kutzi
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: