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

BlueOcean UI stuck in "Waiting for run to start"

    XMLWordPrintable

    Details

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

      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

          Issue Links

            Activity

            Hide
            elliotg Elliot Graebert added a comment - - edited

            I'm also running into the same issue, which I also commented on here: https://issues.jenkins-ci.org/browse/JENKINS-49131

            This issue is very frustrating, as it makes the entire CI pipeline look like it's hung.

             

            Jenkins 2.187 and Blue Ocean 1.18.0

            Show
            elliotg Elliot Graebert added a comment - - edited I'm also running into the same issue, which I also commented on here:  https://issues.jenkins-ci.org/browse/JENKINS-49131 This issue is very frustrating, as it makes the entire CI pipeline look like it's hung.   Jenkins 2.187 and Blue Ocean 1.18.0
            Hide
            rmorrise Russell Morrisey added a comment -

            We updated our plugins over the weekend, but we are still unable to see the input stage to approve PROD deployments.

            This is a show-stopper for us. We are dropping all usage of Blue Ocean (except for new pipeline setup) until it's resolved.

             

            Show
            rmorrise Russell Morrisey added a comment - We updated our plugins over the weekend, but we are still unable to see the input stage to approve PROD deployments. This is a show-stopper for us. We are dropping all usage of Blue Ocean (except for new pipeline setup) until it's resolved.  
            Hide
            timewalker75a Dmitry Seryogin added a comment -

            With jenkins 2.164.1, after updating to 1.17.0 and 1.18 .0 subsequently, we are facing the same issue. We have multiple product versioning and deployment pipelines with when-conditions that alter the stage behaviour. Most pipelines have now been affected byt this problem where stages after when-conditon stages just appear dead with the 'waiting' message.

            Show
            timewalker75a Dmitry Seryogin added a comment - With jenkins 2.164.1, after updating to 1.17.0 and 1.18 .0 subsequently, we are facing the same issue. We have multiple product versioning and deployment pipelines with when-conditions that alter the stage behaviour. Most pipelines have now been affected byt this problem where stages after when-conditon stages just appear dead with the 'waiting' message.
            Hide
            t3rm1 Unknown Unknown added a comment -

            Same here. No input steps are shown. We are not able to finish a pipeline. This is a desaster.

            Show
            t3rm1 Unknown Unknown added a comment - Same here. No input steps are shown. We are not able to finish a pipeline. This is a desaster.
            Hide
            t3rm1 Unknown Unknown added a comment -

            After reading through all the comments I came to the conclusion that Blue Ocean must be dead and abandoned. The issue is over 2 months old and breaks Blue Ocean completly. How is it possible that nobody has fixed this the minute after it was reported.

            Show
            t3rm1 Unknown Unknown added a comment - After reading through all the comments I came to the conclusion that Blue Ocean must be dead and abandoned. The issue is over 2 months old and breaks Blue Ocean completly. How is it possible that nobody has fixed this the minute after it was reported.

              People

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

                Dates

                • Created:
                  Updated: