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

Sometimes missing steps of stage in Blue Ocean Pipeline view

    XMLWordPrintable

    Details

    • Epic Link:
    • Sprint:
      Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3
    • Similar Issues:

      Description

      Scheduled for release

      This fix is scheduled for release as part of Blue Ocean 1.2

      For one specific pipeline it sometimes does not show the steps of (the first) stage:

      Although they are shown in logs:

      [Pipeline] timestamps
      [Pipeline] {
      [Pipeline] lock
      10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
      10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
      [Pipeline] {
      [Pipeline] node
      10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
      [Pipeline] {
      [Pipeline] echo
      10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
      [Pipeline] stage
      [Pipeline] { (checkout)
      [Pipeline] checkout
      10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
      10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
      10:09:25 U         JenkinsPipeline/Jenkinsfile
      10:09:48 At revision 134542
      10:09:48 
      10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
      [Pipeline] echo
      10:09:49 	SVN Revision | Date | Author | Message
      10:09:49 	134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
      10:09:49 		- edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
      [Pipeline] sh
      10:09:50 [**-Pipeline (Branch)] Running shell script
      10:09:50 + ./gradlew --no-daemon zip***All
      10:09:57 :zip*** UP-TO-DATE
      10:09:57 :zip***UnitTests UP-TO-DATE
      10:09:57 :zip***All UP-TO-DATE
      10:09:57 
      10:09:57 BUILD SUCCESSFUL
      10:09:57 
      10:09:57 Total time: 7.35 secs
      [Pipeline] dir
      10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
      [Pipeline] {
      [Pipeline] stash
      10:10:10 Stashed 1 file(s)
      [Pipeline] stash
      10:10:10 Stashed 1 file(s)
      [Pipeline] }
      [Pipeline] // dir
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] }
      10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
      [Pipeline] // lock
      [Pipeline] }
      [Pipeline] // timestamps
      

      ... and steps are also shown correctly in classic UI:

      Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:

      • pipeline-model-definition:1.1.7 (from 1.1.6)
      • workflow-job:2.13 (from 2.12)
      • workflow-multibranch:2.16 (from 2.15)
      • workflow-scm-step:2.6 (from 2.4)
      • docker-commons:1.7
      • docker-workflow:1.12
      • subversion:2.8 (from 2.7.2)
      • blueocean:1.1.2 (from 1.1.1)

      Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur:

      HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header_section selected" and "log-header_section download-log-button"), but not the subsequent sibling div container with class "Steps".

        Attachments

          Issue Links

            Activity

            reinholdfuereder Reinhold Füreder created issue -
            reinholdfuereder Reinhold Füreder made changes -
            Field Original Value New Value
            Description For one specific pipeline it does not show the steps of the first stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although the are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}

            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
            * pipeline-model-definition:1.1.7 (from 1.1.6)
            * workflow-job:2.13 (from 2.12)
            * workflow-multibranch:2.16 (from 2.15)
            * workflow-scm-step:2.6 (from 2.4)
            * docker-commons:1.7
            * docker-workflow:1.12
            * subversion:2.8 (from 2.7.2)
            * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch -- here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!
            For one specific pipeline it does not show the steps of the first stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although the are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}

            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
            * pipeline-model-definition:1.1.7 (from 1.1.6)
            * workflow-job:2.13 (from 2.12)
            * workflow-multibranch:2.16 (from 2.15)
            * workflow-scm-step:2.6 (from 2.4)
            * docker-commons:1.7
            * docker-workflow:1.12
            * subversion:2.8 (from 2.7.2)
            * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch -- here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!


            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            reinholdfuereder Reinhold Füreder made changes -
            Summary Missing steps of first stage in Blue Ocean Pipeline view (for certain pipeline) Sometimes missing steps of stage in Blue Ocean Pipeline view
            Hide
            reinholdfuereder Reinhold Füreder added a comment -

            Further investigations explain the pseudo randomness and the problem:

            • JS error:
              13:27:41.527 [ERROR - io.jenkins.blueocean.dashboard.karaoke.Pager.Pipeline] Error fetching page SyntaxError: JSON.parse: bad character in string literal at line 1 column 1845 of the JSON data 1 blueocean.js:18807:9
              	error https://jenkins.***.com/adjuncts/43b56f6d/io/jenkins/blueocean/blueocean.js:18807:9
              	fetchCurrentStepUrl/< https://jenkins.***.com/adjuncts/43b56f6d/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:51430:17
              
            • The JSON contains unescaped log output from step:
              [Pipeline] echo
              10:09:49 	SVN Revision | Date | Author | Message
              10:09:49 	134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
              10:09:49 		- edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
              
              • whereas the text that is echoed contains a console output link created via
                hudson.console.HyperlinkNote.encodeTo(...)
                
              • ... that presumably need to be escaped or so
            Show
            reinholdfuereder Reinhold Füreder added a comment - Further investigations explain the pseudo randomness and the problem: JS error: 13:27:41.527 [ERROR - io.jenkins.blueocean.dashboard.karaoke.Pager.Pipeline] Error fetching page SyntaxError: JSON.parse: bad character in string literal at line 1 column 1845 of the JSON data 1 blueocean.js:18807:9 error https://jenkins.***.com/adjuncts/43b56f6d/io/jenkins/blueocean/blueocean.js:18807:9 fetchCurrentStepUrl/< https://jenkins.***.com/adjuncts/43b56f6d/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:51430:17 The JSON contains unescaped log output from step: [Pipeline] echo 10:09:49 SVN Revision | Date | Author | Message 10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline) 10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile whereas the text that is echoed contains a console output link created via hudson.console.HyperlinkNote.encodeTo(...) ... that presumably need to be escaped or so
            reinholdfuereder Reinhold Füreder made changes -
            Description For one specific pipeline it does not show the steps of the first stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although the are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}

            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
            * pipeline-model-definition:1.1.7 (from 1.1.6)
            * workflow-job:2.13 (from 2.12)
            * workflow-multibranch:2.16 (from 2.15)
            * workflow-scm-step:2.6 (from 2.4)
            * docker-commons:1.7
            * docker-workflow:1.12
            * subversion:2.8 (from 2.7.2)
            * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch -- here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!


            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although the are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            reinholdfuereder Reinhold Füreder made changes -
            Description For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although the are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although they are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            Hide
            jamesdumay James Dumay added a comment -

            Reinhold Füreder can you share your Jenkinsfile? We can't tell what might be the problem unless we can see it

            Show
            jamesdumay James Dumay added a comment - Reinhold Füreder can you share your Jenkinsfile? We can't tell what might be the problem unless we can see it
            Hide
            jamesdumay James Dumay added a comment - - edited
            Show
            jamesdumay James Dumay added a comment - - edited Reinhold Füreder could you please capture loading the pipeline using a HAR and send the HAR file to me via this secure upload
            jamesdumay James Dumay made changes -
            Assignee James Dumay [ jamesdumay ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta1 [ 336 ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta1 [ 336 ] Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2 [ 336, 341 ]
            reinholdfuereder Reinhold Füreder made changes -
            Attachment image-2017-06-27-07-47-40-685.png [ 38653 ]
            Hide
            reinholdfuereder Reinhold Füreder added a comment -

            James Dumay Thanks for taking care

            With the first comment above I tried to show what the actual problem is: the Steps are not rendered, because the JSON data for the Steps output is invalid, because log data (from an encoded HyperlinkNote) is not escaped; and this also explain why this does not happen all the time...

            Here is a Chrome Developer Tools Console screenshot:

            And I'll send you the requested HAR file via secure upload in a second...

            Show
            reinholdfuereder Reinhold Füreder added a comment - James Dumay Thanks for taking care With the first comment above I tried to show what the actual problem is: the Steps are not rendered, because the JSON data for the Steps output is invalid, because log data (from an encoded HyperlinkNote) is not escaped; and this also explain why this does not happen all the time... Here is a Chrome Developer Tools Console screenshot: And I'll send you the requested HAR file via secure upload in a second...
            jamesdumay James Dumay made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            Hide
            jamesdumay James Dumay added a comment -

            Reinhold Füreder found the problem - in some cases we are not sanitising the step descroption properly. For example, if a step name contains a \t this will cause JSON parsing to fail.

            Show
            jamesdumay James Dumay added a comment - Reinhold Füreder found the problem - in some cases we are not sanitising the step descroption properly. For example, if a step name contains a \t this will cause JSON parsing to fail.
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "PR (Web Link)" [ 17191 ]
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35759 [ 171771 ]
            Hide
            jamesdumay James Dumay added a comment -

            Reinhold Füreder and thank you

            Show
            jamesdumay James Dumay added a comment - Reinhold Füreder and thank you
            Hide
            jamesdumay James Dumay added a comment -

            Candidate for 1.1.3

            Show
            jamesdumay James Dumay added a comment - Candidate for 1.1.3
            Hide
            reinholdfuereder Reinhold Füreder added a comment -

            Glad that you found the problem, thanks James Dumay

            Show
            reinholdfuereder Reinhold Füreder added a comment - Glad that you found the problem, thanks James Dumay
            Hide
            jamesdumay James Dumay added a comment -

            You're more than welcome Reinhold Füreder

            Show
            jamesdumay James Dumay added a comment - You're more than welcome Reinhold Füreder
            jamesdumay James Dumay made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            Hide
            jamesdumay James Dumay added a comment -

            Backported to 1.1.3

            Show
            jamesdumay James Dumay added a comment - Backported to 1.1.3
            Hide
            reinholdfuereder Reinhold Füreder added a comment - - edited

            I have installed BlueOcean 1.1.4, but the problem seems to be still there: please note that I (naively?) assume that the visualization of the old build should work now as well; and for a new build a similar problem occurs (for a different stage)...

            The culprit seems to be again/still invalid JSON response for "steps/" and caused by using 'ansiColor' step based formatting in 'echo' step:

            void logError(String error, String smallHint = '') {
            	ansiColor('xterm') {
            		echo "\033[1;31mPipeline problem: ${error}\033[0m ${smallHint}"
            	}
            }
            

            www.jsonlint.com reports:

             

            In addition the previous cause also seems to still happen (maybe internally it falls back to the same root cause, I don't know):

            hudson.console.HyperlinkNote.encodeTo(...)
            

            Hope the aforementioned details help and thanks in advance for fixing.

            Show
            reinholdfuereder Reinhold Füreder added a comment - - edited I have installed BlueOcean 1.1.4, but the problem seems to be still there: please note that I (naively?) assume that the visualization of the old build should work now as well; and for a new build a similar problem occurs (for a different stage)... The culprit seems to be again/still invalid JSON response for "steps/" and caused by using 'ansiColor' step based formatting in 'echo' step: void logError( String error, String smallHint = '') { ansiColor( 'xterm' ) { echo "\033[1;31mPipeline problem: ${error}\033[0m ${smallHint}" } } www.jsonlint.com reports:   In addition the previous cause also seems to still happen (maybe internally it falls back to the same root cause, I don't know): hudson.console.HyperlinkNote.encodeTo(...) Hope the aforementioned details help and thanks in advance for fixing.
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2 [ 336, 341 ] Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3 [ 336, 341, 346 ]
            Hide
            jamesdumay James Dumay added a comment -

            Reinhold Füreder ill take a look

            Show
            jamesdumay James Dumay added a comment - Reinhold Füreder ill take a look
            jamesdumay James Dumay made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            reinholdfuereder Reinhold Füreder made changes -
            Attachment image-2017-07-12-10-54-52-927.png [ 38835 ]
            devopsguy11 e f made changes -
            Hide
            devopsguy11 e f added a comment -

            I have a similar issue with steps not being displayed in Blue Ocean, while they are displayed in log and classic view

             

            Jenkins ver. 2.60.1
            
            Blue Ocean plugin versions:
            
            blueocean	1.1.4
            blueocean-autofavorite	1.0.0
            blueocean-commons	1.1.4
            blueocean-config	1.1.4
            blueocean-dashboard	1.1.4
            blueocean-display-url	2.0
            blueocean-events	1.1.4
            blueocean-git-pipeline	1.1.4
            blueocean-github-pipeline	1.1.4
            blueocean-i18n	1.1.4
            blueocean-jwt	1.1.4
            blueocean-personalization	1.1.4
            blueocean-pipeline-api-impl	1.1.4
            blueocean-pipeline-editor	0.2.0
            blueocean-pipeline-scm-api	1.1.4
            blueocean-rest	1.1.4
            blueocean-rest-impl	1.1.4
            blueocean-web	1.1.4
            
            

             

            Show
            devopsguy11 e f added a comment - I have a similar issue with steps not being displayed in Blue Ocean, while they are displayed in log and classic view   Jenkins ver. 2.60.1 Blue Ocean plugin versions: blueocean 1.1.4 blueocean-autofavorite 1.0.0 blueocean-commons 1.1.4 blueocean-config 1.1.4 blueocean-dashboard 1.1.4 blueocean-display-url 2.0 blueocean-events 1.1.4 blueocean-git-pipeline 1.1.4 blueocean-github-pipeline 1.1.4 blueocean-i18n 1.1.4 blueocean-jwt 1.1.4 blueocean-personalization 1.1.4 blueocean-pipeline-api-impl 1.1.4 blueocean-pipeline-editor 0.2.0 blueocean-pipeline-scm-api 1.1.4 blueocean- rest 1.1.4 blueocean- rest -impl 1.1.4 blueocean-web 1.1.4  
            Hide
            devopsguy11 e f added a comment -

            Same pipeline is displayed properly in blue ocean for:

             

            Jenkins ver. 2.46.1
            
            blue ocean plugins:
            
            blueocean	1.0.1
            blueocean-autofavorite	0.7
            blueocean-commons	1.0.1
            blueocean-config	1.0.1
            blueocean-dashboard	1.0.1
            blueocean-display-url	2.0
            blueocean-events	1.0.1
            blueocean-git-pipeline	1.0.1
            blueocean-github-pipeline	1.0.1
            blueocean-i18n	1.0.1
            blueocean-jwt	1.0.1
            blueocean-personalization	1.0.1
            blueocean-pipeline-api-impl	1.0.1
            blueocean-pipeline-editor	0.2.0
            blueocean-rest	1.0.1
            blueocean-rest-impl	1.0.1
            blueocean-web	1.0.1
            
            Show
            devopsguy11 e f added a comment - Same pipeline is displayed properly in blue ocean for:   Jenkins ver. 2.46.1 blue ocean plugins: blueocean 1.0.1 blueocean-autofavorite 0.7 blueocean-commons 1.0.1 blueocean-config 1.0.1 blueocean-dashboard 1.0.1 blueocean-display-url 2.0 blueocean-events 1.0.1 blueocean-git-pipeline 1.0.1 blueocean-github-pipeline 1.0.1 blueocean-i18n 1.0.1 blueocean-jwt 1.0.1 blueocean-personalization 1.0.1 blueocean-pipeline-api-impl 1.0.1 blueocean-pipeline-editor 0.2.0 blueocean- rest 1.0.1 blueocean- rest -impl 1.0.1 blueocean-web 1.0.1
            Hide
            devopsguy11 e f added a comment -

            I confirmed that removing below resolves the issue. Unfortunately, we use this in many projects and as such is blocking us from upgrading blue ocean

            ansiColor('xterm') {
                echo "\033[32m some text \033[0m"
            }
            Show
            devopsguy11 e f added a comment - I confirmed that removing below resolves the issue. Unfortunately, we use this in many projects and as such is blocking us from upgrading blue ocean ansiColor( 'xterm' ) { echo "\033[32m some text \033[0m" }
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3 [ 336, 341, 346 ] Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 336, 341, 346, 361 ]
            Hide
            jamesdumay James Dumay added a comment -

            Thanks e f I'm looking into this again.

            Show
            jamesdumay James Dumay added a comment - Thanks e f I'm looking into this again.
            jamesdumay James Dumay made changes -
            Status Reopened [ 4 ] Open [ 1 ]
            jamesdumay James Dumay made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            Hide
            jamesdumay James Dumay added a comment -

            This turned out to be somewhat more nuanced than anticipated but there is now a fix on master. I expect this to be released in the next 1.2 beta which we are likely to release next week.

            Show
            jamesdumay James Dumay added a comment - This turned out to be somewhat more nuanced than anticipated but there is now a fix on master. I expect this to be released in the next 1.2 beta which we are likely to release next week.
            jamesdumay James Dumay made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            jamesdumay James Dumay made changes -
            Description For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although they are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            {panel:title=Scheduled for release|titleBGColor=#3878de|titleColor=white}
            This bug is scheduled for release as part of Blue Ocean 1.2
            {panel}

            For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although they are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            jamesdumay James Dumay made changes -
            Description {panel:title=Scheduled for release|titleBGColor=#3878de|titleColor=white}
            This bug is scheduled for release as part of Blue Ocean 1.2
            {panel}

            For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although they are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            {panel:title=Scheduled for release|titleBGColor=#3878de|titleColor=white}
            This fix is scheduled for release as part of Blue Ocean 1.2
            {panel}

            For one specific pipeline it sometimes does not show the steps of (the first) stage: !image-2017-06-23-11-18-54-169.png|thumbnail!

            Although they are shown in logs:
            {noformat}
            [Pipeline] timestamps
            [Pipeline] {
            [Pipeline] lock
            10:09:18 Trying to acquire lock on [**-Pipeline (Branch)-commit-stage]
            10:09:18 Lock acquired on [**-Pipeline (Branch)-commit-stage]
            [Pipeline] {
            [Pipeline] node
            10:09:19 Running on master in /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] {
            [Pipeline] echo
            10:09:19 Workspace: /var/lib/jenkins/workspace/**-Pipeline (Branch)
            [Pipeline] stage
            [Pipeline] { (checkout)
            [Pipeline] checkout
            10:09:19 Updating https://svn.***.com/svn/***/branches/dev/Jenkins2 at revision '2017-06-23T10:08:27.528 +0200'
            10:09:19 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            10:09:25 U JenkinsPipeline/Jenkinsfile
            10:09:48 At revision 134542
            10:09:48
            10:09:49 Using sole credentials jenkins/****** (SVN server user and password credentials) in realm ‘<https://svn.***.com:443> ***’
            [Pipeline] echo
            10:09:49 SVN Revision | Date | Author | Message
            10:09:49 134542 | 06/23/17 10:08:25 | *** | Dummy commit (to trigger build pipeline)
            10:09:49 - edit: /***/branches/dev/Jenkins2/JenkinsPipeline/Jenkinsfile
            [Pipeline] sh
            10:09:50 [**-Pipeline (Branch)] Running shell script
            10:09:50 + ./gradlew --no-daemon zip***All
            10:09:57 :zip*** UP-TO-DATE
            10:09:57 :zip***UnitTests UP-TO-DATE
            10:09:57 :zip***All UP-TO-DATE
            10:09:57
            10:09:57 BUILD SUCCESSFUL
            10:09:57
            10:09:57 Total time: 7.35 secs
            [Pipeline] dir
            10:09:57 Running in /var/lib/jenkins/workspace/**-Pipeline (Branch)/build-gradle
            [Pipeline] {
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] stash
            10:10:10 Stashed 1 file(s)
            [Pipeline] }
            [Pipeline] // dir
            [Pipeline] }
            [Pipeline] // stage
            [Pipeline] }
            [Pipeline] // node
            [Pipeline] }
            10:10:10 Lock released on resource [**-Pipeline (Branch)-commit-stage]
            [Pipeline] // lock
            [Pipeline] }
            [Pipeline] // timestamps
            {noformat}
            ... and steps are also shown correctly in classic UI: !image-2017-06-23-11-15-57-646.png|thumbnail!

            Not sure if related (because maybe I did not notice that the bug was there before?), but today I updated the following Jenkins plugins:
             * pipeline-model-definition:1.1.7 (from 1.1.6)
             * workflow-job:2.13 (from 2.12)
             * workflow-multibranch:2.16 (from 2.15)
             * workflow-scm-step:2.6 (from 2.4)
             * docker-commons:1.7
             * docker-workflow:1.12
             * subversion:2.8 (from 2.7.2)
             * blueocean:1.1.2 (from 1.1.1)

            Note: I have a second mostly identical pipeline for another branch – here this problem does NOT occur: !image-2017-06-23-11-25-51-170.png|thumbnail!

            HTML code details: for the stage there is still the div container with class "log-header" (with the two div children of "log-header__section selected" and "log-header__section download-log-button"), but not the subsequent sibling div container with class "Steps".
            jamesdumay James Dumay made changes -
            Status Resolved [ 5 ] In Review [ 10005 ]
            Hide
            jamesdumay James Dumay added a comment -

            Ivan Meredith could you look at this one this week? There were some issues on https://github.com/stapler/stapler that needed to be resolved.

            Show
            jamesdumay James Dumay added a comment - Ivan Meredith could you look at this one this week? There were some issues on https://github.com/stapler/stapler that needed to be resolved.
            jamesdumay James Dumay made changes -
            Assignee James Dumay [ jamesdumay ] Ivan Meredith [ imeredith ]
            jamesdumay James Dumay made changes -
            Status In Review [ 10005 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Open [ 1 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 336, 341, 346, 361 ] Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2-beta5 [ 336, 341, 346, 361, 376 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Assignee Ivan Meredith [ imeredith ] Vivek Pandey [ vivek ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2 [ 336, 341, 346, 361, 376 ] Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3 - beta 1 [ 336, 341, 346, 361, 376, 386 ]
            Hide
            michaelneale Michael Neale added a comment -

            I believe this is taken care of with ansi support (colours can still go missing, but that is another issue). Feel free to reopen if there is a misunderstanding.

            Show
            michaelneale Michael Neale added a comment - I believe this is taken care of with ansi support (colours can still go missing, but that is another issue). Feel free to reopen if there is a misunderstanding.
            michaelneale Michael Neale made changes -
            Status Open [ 1 ] Closed [ 6 ]
            Assignee Vivek Pandey [ vivek ]
            Resolution Fixed [ 1 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                reinholdfuereder Reinhold Füreder
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: