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

Pipeline Stage View No Longer Shown After Plugin Upgrade

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • Win 2012, Jenkins 2.19.2, Pipeline Plugin 2.4 Pipeline Stage View 2.2

      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.

          [JENKINS-39541] Pipeline Stage View No Longer Shown After Plugin Upgrade

          Mike Hay added a comment -

          OK thx. I'm on LTS so looks like there is 2.19.3 coming next Wed (Nov 23 2016). Hoping these updates are in there.

          Mike Hay added a comment - OK thx. I'm on LTS so looks like there is 2.19.3 coming next Wed (Nov 23 2016). Hoping these updates are in there.

          Mike Hay added a comment - - edited

          svanoort Do you know if the previous issue you mention (i think it was JENKINS-39555) is tagged for LTS release?

          Mike Hay added a comment - - edited svanoort Do you know if the previous issue you mention (i think it was JENKINS-39555 ) is tagged for LTS release?

          I have the same jenkins version (2.19.2) and same stage view plugin version (2.2) and also not seeing the stages. In dev console i can see
          jquery2.js:998 GET [SERVER_URL]/wfapi/runs?fullStages=true&_=1479837967515 500 (Server Error)
          Are you suggesting upgrade to 2.19.3 or 2.30 ?

          Andrzej Korczynski added a comment - I have the same jenkins version (2.19.2) and same stage view plugin version (2.2) and also not seeing the stages. In dev console i can see jquery2.js:998 GET [SERVER_URL] /wfapi/runs?fullStages=true&_=1479837967515 500 (Server Error) Are you suggesting upgrade to 2.19.3 or 2.30 ?

          Tim Benke added a comment -

          severian I think mhay was referring to the next LTS release after 2.19.2, but in between 2.19.3 was released with only one security fix:
          https://jenkins.io/changelog-stable/

          If there is indeed a regular LTS release today as he mentioned it would be 2.19.4. Until a new LTS release happens your only option is to upgrade to the regular non-LTS weekly release >= 2.30 (currently 2.33).

          Tim Benke added a comment - severian I think mhay was referring to the next LTS release after 2.19.2, but in between 2.19.3 was released with only one security fix: https://jenkins.io/changelog-stable/ If there is indeed a regular LTS release today as he mentioned it would be 2.19.4. Until a new LTS release happens your only option is to upgrade to the regular non-LTS weekly release >= 2.30 (currently 2.33).

          We upgraded to 2.19.3 and it worked! Not sure if it was the upgrade itself or some other issue that was blocking it. We are using block stages if it matters.
          We are not seeing the error 500 from my previous comment. Now there is only a warning "stageview.js:4557 No "data-stageId" on stage."

          Andrzej Korczynski added a comment - We upgraded to 2.19.3 and it worked! Not sure if it was the upgrade itself or some other issue that was blocking it. We are using block stages if it matters. We are not seeing the error 500 from my previous comment. Now there is only a warning "stageview.js:4557 No "data-stageId" on stage."

          Sam Van Oort added a comment -

          mkaczorowski 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)

          Sam Van Oort added a comment - mkaczorowski 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)

          svanoort Will test and report back. Thanks

          Matt Kaczorowski added a comment - svanoort Will test and report back. Thanks

          Sam Van Oort added a comment -

          mkaczorowski 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).

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

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

          Sam Van Oort added a comment - mkaczorowski 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). severian The issue you see is with "No data-stageID" is JENKINS-37910 – it is ugly but totally harmless. mhay If you wouldn't mind updating your core & plugins, if that resolves this we can consider this solved.

          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

          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

          Sam Van Oort added a comment -

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

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

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

              Created:
              Updated:
              Resolved: