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

Sometimes missing steps of stage in Blue Ocean Pipeline view

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • blueocean-plugin
    • None
    • 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

      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".

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

              Created:
              Updated:
              Resolved: