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

BlueOcean UI stuck in "Waiting for run to start"

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.180, BlueOcean 1.17.0
    • Similar Issues:
    • Released As:
      blue-ocean 1.19.0

      Description

      We recently upgraded BlueOcean from 1.16.0 to 1.17.0 and we started observing a weird behaviour in the BlueOcean pipeline UI.

      Frequently (not always) the pipeline UI stops updating the progress while the pipeline is running and the UI is stuck at "Waiting for run to start" (see attached screenshot). When it happens, it does not recover until the pipeline execution completes: once completed, the UI is correctly updated (all steps are green).

      We've also noticed that - when happens - the underlying requests sent by the browser to the endpoint https://jenkins.DOMAIN/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/master/runs/ID/nodes/ID/steps/ always return an empty array "[]" instead of the expected array of steps. On the contrary, during the execution of the pipeline, if we look at the "Console Output" (old Jenkins UI) we can correctly see the progress of the pipeline even when the BlueOcean UI is stuck at "Waiting for run to start".

      This issue looks disappear if we rollback all BlueOcean plugins from 1.17.0 to 1.16.0.

        Attachments

        1. jenkins_build1.mov
          970 kB
        2. jenkins_build1.png
          jenkins_build1.png
          89 kB
        3. jenkins_build2.mov
          1.07 MB
        4. jenkins_build2.png
          jenkins_build2.png
          96 kB
        5. screenshot_2019-06-18_at_14.52.11.png
          screenshot_2019-06-18_at_14.52.11.png
          116 kB
        6. Screenshot 2019-10-17 at 10.08.17.png
          Screenshot 2019-10-17 at 10.08.17.png
          16 kB

          Issue Links

            Activity

            Hide
            brianjmurrell Brian J Murrell added a comment -

            Devin Nusbaum A screenshot of the graph for the pipeline when in this state looks just like the existing two screenshots.

            Show
            brianjmurrell Brian J Murrell added a comment - Devin Nusbaum A screenshot of the graph for the pipeline when in this state looks just like the existing two screenshots.
            Hide
            dnusbaum Devin Nusbaum added a comment -

            Brian J Murrell Yes, I mean for Ian Wallace-Hoyt's Pipeline in particular, since we have the associated Jenkinsfile we could use the graph to see what other stages are being shown or not and in what state. Even better would be to have a screenshot of the graph from build with the issue and a screenshot of the graph for the previous build, since the problem relates to how those graphs are being combined.

            Show
            dnusbaum Devin Nusbaum added a comment - Brian J Murrell Yes, I mean for Ian Wallace-Hoyt 's Pipeline in particular, since we have the associated Jenkinsfile we could use the graph to see what other stages are being shown or not and in what state. Even better would be to have a screenshot of the graph from build with the issue and a screenshot of the graph for the previous build, since the problem relates to how those graphs are being combined.
            Hide
            ian_ookla Ian Wallace-Hoyt added a comment -

            Devin Nusbaum

             

            I opened a new PR and let it build. When it completed successfully, I rebuilt it. Same thing in both cases, the "Buddy: build apks" stage shows a queued.

             

            I took the screenshots and video after verifying that the stage was actually building but looking at the node view.

             

            jenkins_build1.png

            jenkins_build1.mov

            jenkins_buld2.png

            jenkins_buld2.mov

             

            Show
            ian_ookla Ian Wallace-Hoyt added a comment - Devin Nusbaum   I opened a new PR and let it build. When it completed successfully, I rebuilt it. Same thing in both cases, the "Buddy: build apks" stage shows a queued.   I took the screenshots and video after verifying that the stage was actually building but looking at the node view.   jenkins_build1.png jenkins_build1.mov jenkins_buld2.png jenkins_buld2.mov  
            Hide
            rankylau Ranky Lau added a comment -

            Is there anyone working at this issue right now?

            Show
            rankylau Ranky Lau added a comment - Is there anyone working at this issue right now?
            Hide
            borisivan boris ivan added a comment -

            this one really hurts, hoping it can be fixed since it really is a bug and not an enhancement.

            Show
            borisivan boris ivan added a comment - this one really hurts, hoping it can be fixed since it really is a bug and not an enhancement.

              People

              • Assignee:
                Unassigned
                Reporter:
                pracucci Marco Pracucci
              • Votes:
                27 Vote for this issue
                Watchers:
                36 Start watching this issue

                Dates

                • Created:
                  Updated: