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

Blue Ocean pipeline shows no progress

    Details

    • Similar Issues:

      Description

      After upgrading pipeline-model-definition 1.38 to 1.39, I started seeing strange behavior in one declarative pipeline. Unfortunately it's a complicated pipeline and I haven't had time to come up with a minimal case to reproduce the issue.

       

      In some situations, the Blue Ocean UI doesn't show progress. It appears as if the build hasn't started yet, even though it has (i.e. go to the console output in the classic UI, and the build is running).  When the build gets to an input prompt, the header bar of Blue Ocean turns the "input prompt blue", but no prompt is visible, and no progress is still shown. It's necessary to navigate to the "classic" UI to respond to the prompt.

       

      The pipeline has a call to `input()` in the steps of its first stage. I don't know if this is relevant. I haven't seen the problem in our other pipelines, or even in an obviously reproducible way with the pipeline that does exhibit the issue. Downgrading to pipeline-model-definition:1.38 fixes the issue. Sorry for the vague report. I had to do the downgrade quickly to unblock my teammates, and didn't have time to investigate thoroughly.

        Attachments

          Issue Links

            Activity

            Hide
            jonathanb1 Jonathan B added a comment - - edited

            After I posted this, the issue came up again despite having downgraded to pipeline-model-definition 1.38, so this ticket misattributes the problem. There's still an issue, but I don't know where it lies. The upgrade that introduced the problem was Jenkins 2.164.2 > 2.176.1, with potentially-relevant-looking plugin changes:

            blueocean 1.16.0 -> 1.17.0
            git-client 2.7.7 -> 2.8.0
            pipeline-model-api 1.3.8 -> 1.3.9
            pipeline-model-definition 1.3.8 -> 1.3.9
            pipeline-model-extension 1.3.8 -> 1.3.9
            scm-api 2.4.1 -> 2.5.1
            workflow-api 2.34 -> 2.35
            workflow-basic-steps 2.16 -> 2.18
            workflow-cps 2.69 -> 2.70
            workflow-durable-task-step 2.30 -> 2.31
            workflow-scm-step 2.7 -> 2.9
            workflow-step-api 2.19 -> 2.20 

            Any thoughts or suggestions for debugging would be appreciated.

            Show
            jonathanb1 Jonathan B added a comment - - edited After I posted this, the issue came up again despite having downgraded to pipeline-model-definition 1.38, so this ticket misattributes the problem. There's still an issue, but I don't know where it lies. The upgrade that introduced the problem was Jenkins 2.164.2 > 2.176.1, with potentially-relevant-looking plugin changes: blueocean 1.16.0 -> 1.17.0 git-client 2.7.7 -> 2.8.0 pipeline-model-api 1.3.8 -> 1.3.9 pipeline-model-definition 1.3.8 -> 1.3.9 pipeline-model-extension 1.3.8 -> 1.3.9 scm-api 2.4.1 -> 2.5.1 workflow-api 2.34 -> 2.35 workflow-basic-steps 2.16 -> 2.18 workflow-cps 2.69 -> 2.70 workflow-durable-task-step 2.30 -> 2.31 workflow-scm-step 2.7 -> 2.9 workflow-step-api 2.19 -> 2.20  Any thoughts or suggestions for debugging would be appreciated.
            Hide
            t3rm1 Unknown Unknown added a comment -

            I have the same problem. I also updated from 164 to 176. Every pipeline with an input step is not able to complete because the input step just doesn't show up in the Blue Ocean view. The log says "Input requested" and I can click on that link and it also shows me the proceed and abort buttons. I also updated several plugins so I don't know which version caused the error.

             

            Show
            t3rm1 Unknown Unknown added a comment - I have the same problem. I also updated from 164 to 176. Every pipeline with an input step is not able to complete because the input step just doesn't show up in the Blue Ocean view. The log says "Input requested" and I can click on that link and it also shows me the proceed and abort buttons. I also updated several plugins so I don't know which version caused the error.  

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                jonathanb1 Jonathan B
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: