Error steps may change to show up as errors in pipeline view

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Notes
      This issue needs further investigation

      Original request
      In one of our more complex scripted pipelines with special exception/error handling, the error step visualization keeps changing after a while, so that it does not show the error step as failing anymore (and so also no auto-scroll to error works)!?

      I tried to reproduce it to no avail; this is the basic pipeline code (the last and active section in the code being the closest to the original one):

      node {
          // OK:
          /*
          stage('failing-stage') {
              echo 'hello'
              error 'fail on purpose...'
          }
          */
          
          // OK: shows msg in red and expands it
          /*
          stage('failing-stage') {
              echo 'hello'
              try {
                  error 'fail on purpose...'
              } catch (e) {
                  echo "Caught exception: ${e}"
              }
          }
          */
      
          // OK: shows msg in red and expands it
          /*
          stage('failing-stage') {
              echo 'hello'
              try {
                  error 'fail on purpose...'
              } catch (e) {
                  echo "Caught exception: ${e}"
                  throw e
              }
          }
          */
      
          // OK: shows msg in red and expands it
          stage('failing-stage') {
              echo 'hello'
              try {
                  error 'fail on purpose...'
              } catch (e) {
                  ansiColor('xterm') {
                    echo "\033[1;31mCaught exception: ${e}\033[0m bla bla"
                  }
                  throw e
              } finally {
                  echo "finally"
              }
          }
      }
      

      Initially it works fine and looks like this:

      But at one point it stops showing the error step as error! And the AJAX request that fetches the steps (e.g. https://<JENKINS URL>/blue/rest/organizations/jenkins/pipelines/My-Pipeline/runs/414/nodes/60/steps/) shows matching symptoms:

            Assignee:
            Unassigned
            Reporter:
            Reinhold Füreder
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: