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

Stage View shows incorrect build result

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      pipeline-stage-view 2.13

      Description

      Jenkins 2.54 + Pipeline 2.5

      I am seeing all stages passing but Stage View would render builds as failure.

      Blue Ocean seems fine not having the same issue.

       

      Please see screenshot.

        Attachments

        1. blueocean.PNG
          blueocean.PNG
          16 kB
        2. JENKINS-43556.py
          2 kB
        3. jenkinsfile_sanitized.txt
          10 kB
        4. stageview.PNG
          stageview.PNG
          74 kB
        5. StageView.png
          StageView.png
          71 kB

          Issue Links

            Activity

            Hide
            f00f Hannes Strautmann added a comment -

            We are also experiencing this issue lately, randomly. We have not deleted any builds nor reset the next build number.

            Jenkins LTS 2.190.2, all plugins "up to date" (not older than say 4 weeks).

            Same observations as Russell Gallop:

            The normal api for the build: <job>/<buildnum>/api/python?pretty=true says "result": "SUCCESS"
            The wfapi: <job>/wfapi/runs shows <buildnum> as having "status": "FAILED" . All stages within that report "SUCCESS".

            Show
            f00f Hannes Strautmann added a comment - We are also experiencing this issue lately, randomly. We have not deleted any builds nor reset the next build number. Jenkins LTS 2.190.2, all plugins "up to date" (not older than say 4 weeks). Same observations as Russell Gallop : The normal api for the build: <job>/<buildnum>/api/python?pretty=true says "result": "SUCCESS" The wfapi: <job>/wfapi/runs shows <buildnum> as having "status": "FAILED" . All stages within that report "SUCCESS".
            Hide
            slonopotamusorama Marat Radchenko added a comment -

            Confirming what Hannes Strautmann said in previous comment. I also observe situation where wfapi/runs reports FAILED for build that is actually successful.

            Show
            slonopotamusorama Marat Radchenko added a comment - Confirming what Hannes Strautmann said in previous comment. I also observe situation where wfapi/runs reports FAILED for build that is actually successful.
            Hide
            slonopotamusorama Marat Radchenko added a comment -

            Note that PR#75 was merged. While it doesn't fix the root issue (invalid data getting into RunExt cache), it will catch and invalidate bogus cached data when it is got from cache.

            This change wasn't yet released in any pipeline-stage-view-plugin version.

            Show
            slonopotamusorama Marat Radchenko added a comment - Note that PR#75 was merged. While it doesn't fix the root issue (invalid data getting into RunExt cache), it will catch and invalidate bogus cached data when it is got from cache. This change wasn't yet released in any pipeline-stage-view-plugin version.
            Hide
            kon Kalle Niemitalo added a comment -

            I was able to remove the incorrect data from the cache by calling com.cloudbees.workflow.flownode.FlowNodeUtil.CacheExtension.all().get(0).getRunCache().invalidate("the externalizable ID of the run") from the script console.

            Before that, I had tried "Reload Configuration from Disk" under "Manage Jenkins", but it had not cleared the cache, even though its description appears to say otherwise: "Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk."

            Show
            kon Kalle Niemitalo added a comment - I was able to remove the incorrect data from the cache by calling com.cloudbees.workflow.flownode.FlowNodeUtil.CacheExtension.all().get(0).getRunCache().invalidate("the externalizable ID of the run") from the script console. Before that, I had tried "Reload Configuration from Disk" under "Manage Jenkins", but it had not cleared the cache, even though its description appears to say otherwise: "Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk."
            Hide
            raihaan Raihaan Shouhell added a comment -

            Should be resolved please reopen if you encounter this issue again

            Show
            raihaan Raihaan Shouhell added a comment - Should be resolved please reopen if you encounter this issue again

              People

              Assignee:
              raihaan Raihaan Shouhell
              Reporter:
              mocsharp mocsharp
              Votes:
              16 Vote for this issue
              Watchers:
              27 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: