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

Declarative Pipeline shows SUCCESS even though job FAILED

    • pipeline-model-definition 1.3.7

      Pipelines are "failing" with SUCCESS status. 

      This pipeline, taken from JENKINS-46325 illustrates this issue successfully:

      pipeline {
          agent any
          stages {
              stage ('Init') {
                  steps {
                      echo "Init result: ${currentBuild.result}"
                      echo "Init currentResult: ${currentBuild.currentResult}"
                  }
                  post {
                      always {
                          echo "Post-Init result: ${currentBuild.result}"
                          echo "Post-Init currentResult: ${currentBuild.currentResult}"
                      }
                  }
              }
              stage ('Build') {
                  steps {
                      echo "During Build result: ${currentBuild.result}"
                      echo "During Build currentResult: ${currentBuild.currentResult}"
                      sh 'exit 1'
                  }
                  post {
                      always {
                          echo "Post-Build result: ${currentBuild.result}"
                          echo "Post-Build currentResult: ${currentBuild.currentResult}"
                      }
                  }
              }
          }
          post {
              always {
                  echo "Pipeline result: ${currentBuild.result}"
                  echo "Pipeline currentResult: ${currentBuild.currentResult}"
              }
          }
      }
      

       

      My results are (trimmed down):

      Running on build-096575a3-e6af-4fff-9ca1-84cc46ba4b86-f9b8d29c in /var/vcap/data/jenkins-slave/workspace/test-job
      Init result: null
      Init currentResult: SUCCESS
      Post stage
      Post-Init result: null
      Post-Init currentResult: SUCCESS
      During Build result: null
      During Build currentResult: SUCCESS
      [Pipeline] sh
      + exit 1
      Post stage
      Post-Build result: null
      Post-Build currentResult: SUCCESS
      Pipeline result: null
      Pipeline currentResult: SUCCESS
      ERROR: script returned exit code 1
      Finished: FAILURE
      

       

          [JENKINS-56402] Declarative Pipeline shows SUCCESS even though job FAILED

          Philip Zozobrado created issue -
          Philip Zozobrado made changes -
          Description Original: Pipelines are "failing" with SUCCESS status. 

          This pipeline, taken from JENKINS-46325 illustrates this issues successfully:
          {code}
          pipeline {
              agent any
              stages {
                  stage ('Init') {
                      steps {
                          echo "Init result: ${currentBuild.result}"
                          echo "Init currentResult: ${currentBuild.currentResult}"
                      }
                      post {
                          always {
                              echo "Post-Init result: ${currentBuild.result}"
                              echo "Post-Init currentResult: ${currentBuild.currentResult}"
                          }
                      }
                  }
                  stage ('Build') {
                      steps {
                          echo "During Build result: ${currentBuild.result}"
                          echo "During Build currentResult: ${currentBuild.currentResult}"
                          sh 'exit 1'
                      }
                      post {
                          always {
                              echo "Post-Build result: ${currentBuild.result}"
                              echo "Post-Build currentResult: ${currentBuild.currentResult}"
                          }
                      }
                  }
              }
              post {
                  always {
                      echo "Pipeline result: ${currentBuild.result}"
                      echo "Pipeline currentResult: ${currentBuild.currentResult}"
                  }
              }
          }
          {code}
           

          My results are (trimmed down):
          {noformat}
          Running on build-096575a3-e6af-4fff-9ca1-84cc46ba4b86-f9b8d29c in /var/vcap/data/jenkins-slave/workspace/test-job
          Init result: null
          Init currentResult: SUCCESS
          Post stage
          Post-Init result: null
          Post-Init currentResult: SUCCESS
          During Build result: null
          During Build currentResult: SUCCESS
          [Pipeline] sh
          + exit 1
          Post stage
          Post-Build result: null
          Post-Build currentResult: SUCCESS
          Pipeline result: null
          Pipeline currentResult: SUCCESS
          ERROR: script returned exit code 1
          Finished: FAILURE
          {noformat}
           
          New: Pipelines are "failing" with SUCCESS status. 

          This pipeline, taken from JENKINS-46325 illustrates this issue successfully:
          {code:java}
          pipeline {
              agent any
              stages {
                  stage ('Init') {
                      steps {
                          echo "Init result: ${currentBuild.result}"
                          echo "Init currentResult: ${currentBuild.currentResult}"
                      }
                      post {
                          always {
                              echo "Post-Init result: ${currentBuild.result}"
                              echo "Post-Init currentResult: ${currentBuild.currentResult}"
                          }
                      }
                  }
                  stage ('Build') {
                      steps {
                          echo "During Build result: ${currentBuild.result}"
                          echo "During Build currentResult: ${currentBuild.currentResult}"
                          sh 'exit 1'
                      }
                      post {
                          always {
                              echo "Post-Build result: ${currentBuild.result}"
                              echo "Post-Build currentResult: ${currentBuild.currentResult}"
                          }
                      }
                  }
              }
              post {
                  always {
                      echo "Pipeline result: ${currentBuild.result}"
                      echo "Pipeline currentResult: ${currentBuild.currentResult}"
                  }
              }
          }
          {code}
           

          My results are (trimmed down):
          {noformat}
          Running on build-096575a3-e6af-4fff-9ca1-84cc46ba4b86-f9b8d29c in /var/vcap/data/jenkins-slave/workspace/test-job
          Init result: null
          Init currentResult: SUCCESS
          Post stage
          Post-Init result: null
          Post-Init currentResult: SUCCESS
          During Build result: null
          During Build currentResult: SUCCESS
          [Pipeline] sh
          + exit 1
          Post stage
          Post-Build result: null
          Post-Build currentResult: SUCCESS
          Pipeline result: null
          Pipeline currentResult: SUCCESS
          ERROR: script returned exit code 1
          Finished: FAILURE
          {noformat}
           
          Philip Zozobrado made changes -
          Environment Original: Jenkins 2.150.3, using a slave build executioner New: Jenkins 2.150.3, Pipeline 2.6, using a slave build executioner
          Devin Nusbaum made changes -
          Component/s New: pipeline-model-definition-plugin [ 21706 ]
          Component/s Original: pipeline [ 21692 ]
          Devin Nusbaum made changes -
          Link New: This issue relates to JENKINS-55459 [ JENKINS-55459 ]
          Lakshya Kapoor made changes -
          Comment [ Test. ]
          Andrew Bayer made changes -
          Link New: This issue is duplicated by JENKINS-56430 [ JENKINS-56430 ]
          Steffen Wilke made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]
          Steffen Wilke made changes -
          Environment Original: Jenkins 2.150.3, Pipeline 2.6, using a slave build executioner New: Jenkins 2.150.3, Pipeline 2.6, Pipeline: Declarative plugin v1.3.5, using a slave build executioner
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-56536 [ JENKINS-56536 ]
          Benjamin Kihm made changes -
          Link New: This issue causes JENKINS-44322 [ JENKINS-44322 ]

            Unassigned Unassigned
            pzozobrado Philip Zozobrado
            Votes:
            23 Vote for this issue
            Watchers:
            42 Start watching this issue

              Created:
              Updated: