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

BlueOcean UI stuck in "Waiting for run to start"

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • blueocean-plugin
    • None
    • Jenkins 2.180, BlueOcean 1.17.0
    • blue-ocean 1.19.0

      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.

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

          [JENKINS-58085] BlueOcean UI stuck in "Waiting for run to start"

          Marco Pracucci created issue -

          I'm running into this same exact issue as well after upgrading to BlueOcean 1.17.0 (currently on Jenkins 2.181)

           

           

          Diego Rodriguez added a comment - I'm running into this same exact issue as well after upgrading to BlueOcean 1.17.0 (currently on Jenkins 2.181)    

          Pietro Pepe added a comment -

          Also in our infrastructure we get the same issue using BlueOcean 1.17.0 (on Jenkins 2.176.1)

          Pietro Pepe added a comment - Also in our infrastructure we get the same issue using BlueOcean 1.17.0 (on Jenkins 2.176.1)
          Pietro Pepe made changes -
          Assignee New: Pietro Pepe [ ppepe ]
          Pietro Pepe made changes -
          Assignee Original: Pietro Pepe [ ppepe ]

          Jonathan B added a comment - - edited

          We're also experiencing this after an upgrade to BlueOcean 1.17.0 and Jenkins 2.176.1. I filed https://issues.jenkins-ci.org/browse/JENKINS-58145 about it.

          I tried downgrading BlueOcean  back to 1.16.0 but that didn't actually help. I also tried downgrading all the pipeline-model* plugins from 1.39 back to 1.38 (which was the version we were on when this was working properly), but that also did not help.

          From my hasty testing, my best guess right now is that the issue was introduced by one of workflow-step-api:2.20 (2.19 was fine), workflow-durable-task-step:2.31 (2.30 was fine), or workflow-cps:2.70 (2.69 was fine). Those are tricky to downgrade because there is some complicated web of dependencies that require us to be on the latest of all of them.

          Since you mention that downgrading BlueOcean to 1.16 fixed it for you, I will have to try that again.

          Jonathan B added a comment - - edited We're also experiencing this after an upgrade to BlueOcean 1.17.0 and Jenkins 2.176.1. I filed https://issues.jenkins-ci.org/browse/JENKINS-58145  about it. I tried downgrading BlueOcean  back to 1.16.0 but that didn't actually help. I also tried downgrading all the pipeline-model* plugins from 1.39 back to 1.38 (which was the version we were on when this was working properly), but that also did not help. From my hasty testing, my best guess right now is that the issue was introduced by one of workflow-step-api:2.20 (2.19 was fine), workflow-durable-task-step:2.31 (2.30 was fine), or workflow-cps:2.70 (2.69 was fine). Those are tricky to downgrade because there is some complicated web of dependencies that require us to be on the latest of all of them. Since you mention that downgrading BlueOcean to 1.16 fixed it for you, I will have to try that again.

          jonathanb1 Downgrading to BlueOcean 1.16 worked for us. Pay attention that - to us - to correctly downgrade we had to uninstall all BlueOcean 1.17 plugins first, and then re-installed all of them (one by one) on 1.16 version without using the "blueocean:1.16" meta package which was re-installing the 1.17 version of plugins. Don't know if there's an easier way, or this downgrade issue was due to our setup (we didn't investigate much cause we were buried with work).

          Marco Pracucci added a comment - jonathanb1 Downgrading to BlueOcean 1.16 worked for us. Pay attention that - to us - to correctly downgrade we had to uninstall all BlueOcean 1.17 plugins first, and then re-installed all of them (one by one) on 1.16 version without using the "blueocean:1.16" meta package which was re-installing the 1.17 version of plugins. Don't know if there's an easier way, or this downgrade issue was due to our setup (we didn't investigate much cause we were buried with work).
          Jonathan B made changes -
          Link New: This issue is duplicated by JENKINS-58145 [ JENKINS-58145 ]

          Jonathan B added a comment - - edited

          pracucci thank you. I revisited this and downgrading to Blue Ocean 1.16 did resolve the issue here as well. When I tried initially, I had downgraded only the metapackage `blueocean`, but all of the subpackages were still on 1.17.

          Jonathan B added a comment - - edited pracucci thank you. I revisited this and downgrading to Blue Ocean 1.16 did resolve the issue here as well. When I tried initially, I had downgraded only the metapackage `blueocean`, but all of the subpackages were still on 1.17.

          Reinhold Füreder added a comment - - edited

          We are also experiencing this huge problem (but not all the time though!?) – but are hesitating to downgrade, as 1.17 contains one really, really helpful new feature: JENKINS-39203 (dnusbaum Based on the BlueOcean changelog one naively assumes that this issue is actually caused by JENKINS-39203 => therefore I naively linked this issues)

          Reinhold Füreder added a comment - - edited We are also experiencing this huge problem (but not all the time though!?) – but are hesitating to downgrade, as 1.17 contains one really, really helpful new feature: JENKINS-39203 ( dnusbaum Based on the BlueOcean changelog one naively assumes that this issue is actually caused by JENKINS-39203 => therefore I naively linked this issues)

            Unassigned Unassigned
            pracucci Marco Pracucci
            Votes:
            44 Vote for this issue
            Watchers:
            61 Start watching this issue

              Created:
              Updated: