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

Missing ErrorAction after Jenkins restart

    XMLWordPrintable

Details

    Description

      On Jenkins restart FlowNode corresponding to ErrorStep has missing ErrorAction. I tried this script:

      node {
          stage('stage1') {
              sh "echo 42"
              error("this error should appear in log")       
          }
      }
      

      On executing this script, FlowNode corresponding to error step has ErrorAction. The error message "this error should appear in log" can be seen by hovering over stage view UI. After restart, error step flow node has no such ErrorAction, try hovering over stage view UI and it won't show the error message.

      Persisted XML file for that error step seems to have correct ErrorAction with error message and stack trace but somehow its not de-serialized.

      There seems to be problem in general, take a look at https://github.com/jenkinsci/blueocean-plugin/commit/213854399c924919b7afb7160819a7f0b892dd19, here ExplodingStep has both ErrorAction and LogAction, but they are missing after jenkins restart.

      We are trying to capture failing step's error messages and show them in blueocean UI, it breaks the behavior on jenkins restart.

      After executing the script:

      Stage view:

      Blue Ocean:

      After restart:

      Stage view:

      Blue Ocean:

      Attachments

        Issue Links

          Activity

            vivek Vivek Pandey added a comment -

            Works as expected with workflow-api 2.7 and workflow-basic-steps-2.3 bundled with blueocean. Closing it as no more work needed on it.

            vivek Vivek Pandey added a comment - Works as expected with workflow-api 2.7 and workflow-basic-steps-2.3 bundled with blueocean. Closing it as no more work needed on it.
            vivek Vivek Pandey added a comment -

            campbellr Works as expected with bundled workflow-api 2.7 and workflow-basic-steps-2.3 with blueocean! Looks like got fixed along the way.

            vivek Vivek Pandey added a comment - campbellr Works as expected with bundled workflow-api 2.7 and workflow-basic-steps-2.3 with blueocean! Looks like got fixed along the way.
            jglick Jesse Glick added a comment -

            Working for me in CloudBees Jenkins Enterprise 2.32.2.1-rolling (for sake of concrete plugin versions). Looks the same in stage view after restart.

            jglick Jesse Glick added a comment - Working for me in CloudBees Jenkins Enterprise 2.32.2.1-rolling (for sake of concrete plugin versions). Looks the same in stage view after restart.
            abayer Andrew Bayer added a comment -

            vivek Are both ErrorAction and LogAction missing on restart? Do you have a test case that reproduces this?

            abayer Andrew Bayer added a comment - vivek Are both ErrorAction and LogAction missing on restart? Do you have a test case that reproduces this?
            jglick Jesse Glick added a comment -

            Not that I am aware.

            jglick Jesse Glick added a comment - Not that I am aware.
            svanoort Sam Van Oort added a comment -

            vivek See if this still occurs with the latest plugin versions – I think it might be covered by some of the work jglick did recently.

            svanoort Sam Van Oort added a comment - vivek See if this still occurs with the latest plugin versions – I think it might be covered by some of the work jglick did recently.
            svanoort Sam Van Oort added a comment -

            Yes, recampbell possibly a Bismuth bug of some flavor – or something in the internals. Either way I can investigate. Not today probably, but soon.

            svanoort Sam Van Oort added a comment - Yes, recampbell possibly a Bismuth bug of some flavor – or something in the internals. Either way I can investigate. Not today probably, but soon.
            recampbell Ryan Campbell added a comment -

            svanoort, this looks like a bug in Bismuth, no? If so, something for a followup with the other issues in this area after your current work.

            recampbell Ryan Campbell added a comment - svanoort , this looks like a bug in Bismuth, no? If so, something for a followup with the other issues in this area after your current work.

            People

              Unassigned Unassigned
              vivek Vivek Pandey
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: