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

Pipeline Stage View No Longer Shown After Plugin Upgrade

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: pipeline-stage-view-plugin
    • Labels:
      None
    • Environment:
      Win 2012, Jenkins 2.19.2, Pipeline Plugin 2.4 Pipeline Stage View 2.2
    • Similar Issues:

      Description

      After upgrading my plugins on Nov 4 I no longer see any stage views for my pipeline jobs.

      Win 2012, Jenkins 2.19.2, Pipeline Plugin 2.4 Pipeline Stage View 2.2

      I do not see any errors in the jenkins logs.

      This does not seem to effect the pipeline execution, just the display of the stages on the pipeline job. See attached screen cap that should display 5 stages, no stages are shown.

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-38089 Unexpected Exception during accessing json pipeline status

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39555 Stage view is empty

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            15 older comments
            Hide
            Permalink
            svanoort Sam Van Oort added a comment -

            Matt Kaczorowski Can you confirm if this is still occurring when you update to core 2.19.3 and updating all pipeline plugins?

            I think this is resolved by the fix to JENKINS-39555 or one of the other pipeline fixes (a transitory error introduced by an upstream dependency, probably workflow-api or workflow-support)

            Show
            svanoort Sam Van Oort added a comment - Matt Kaczorowski Can you confirm if this is still occurring when you update to core 2.19.3 and updating all pipeline plugins? I think this is resolved by the fix to JENKINS-39555 or one of the other pipeline fixes (a transitory error introduced by an upstream dependency, probably workflow-api or workflow-support)
            Hide
            Permalink
            mkaczorowski Matt Kaczorowski added a comment -

            Sam Van Oort Will test and report back. Thanks

            Show
            mkaczorowski Matt Kaczorowski added a comment - Sam Van Oort Will test and report back. Thanks
            Hide
            Permalink
            svanoort Sam Van Oort added a comment -

            Matt Kaczorowski You have a different issue at play than the others, based on JENKINS-38089 – I've got a fix for that almost ready to go, which is tested to resolve the issue (there's some other weirdness that I'm sorting out from the same timeframe though, before I feel comfortable releasing it).

            Andrzej Korczynski The issue you see is with "No data-stageID" is JENKINS-37910 – it is ugly but totally harmless.

            Mike Hay If you wouldn't mind updating your core & plugins, if that resolves this we can consider this solved.

            Show
            svanoort Sam Van Oort added a comment - Matt Kaczorowski You have a different issue at play than the others, based on JENKINS-38089 – I've got a fix for that almost ready to go, which is tested to resolve the issue (there's some other weirdness that I'm sorting out from the same timeframe though, before I feel comfortable releasing it). Andrzej Korczynski The issue you see is with "No data-stageID" is JENKINS-37910 – it is ugly but totally harmless. Mike Hay If you wouldn't mind updating your core & plugins, if that resolves this we can consider this solved.
            Hide
            Permalink
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Sam Van Oort
            Path:
            src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScanner.java
            src/test/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScannerTest.java
            http://jenkins-ci.org/commit/workflow-api-plugin/21ada245d8634aef0b33d148aef9a9638c494f1b
            Log:
            Fix JENKINS-39541 which is triggered by a very specific edge case with finding the start node for a complex set of parallels

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScanner.java src/test/java/org/jenkinsci/plugins/workflow/graphanalysis/ForkScannerTest.java http://jenkins-ci.org/commit/workflow-api-plugin/21ada245d8634aef0b33d148aef9a9638c494f1b Log: Fix JENKINS-39541 which is triggered by a very specific edge case with finding the start node for a complex set of parallels
            Hide
            Permalink
            svanoort Sam Van Oort added a comment -

            Closing because from what I can tell, this is a result of other issues, now resolved.

            Show
            svanoort Sam Van Oort added a comment - Closing because from what I can tell, this is a result of other issues, now resolved.

              People

              Assignee:
              svanoort Sam Van Oort
              Reporter:
              mhay Mike Hay
              Votes:
              11 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: