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

Workflow jobs that are waiting for input should have a visual cue in build history

      When a Workflow job is waiting for input, the current visual cue for that is that the ball blinks when you look at the job history. It doesn't blink on the main Jenkins job list page. Further, if you restart Jenkins, the ball for paused jobs stops blinking even though they're still paused and can be resumed.

      I'm not a fan of the blinking ball visual cue because all of my users keep seeing that and thinking their jobs are "stuck" or "still building" or whatever. I think we need a special badge or ball color or something to make it clear that the job is in the 'waiting for input' state. It would also be ideal if this was visible on the Jenkins main page as well.

          [JENKINS-31118] Workflow jobs that are waiting for input should have a visual cue in build history

          Owen Mehegan created issue -

          Jesse Glick added a comment -

          Yes this is a long-discussed RFE. With the stage view (at job level) you do get a special badge on those build rows waiting for input, which could be made more prominent, but anyway we still need some mechanism (on a view page, perhaps) for showing you all builds of any job awaiting approval (ideally filtered by those you could actually approve, when submitter is specified). Adding a list view column is too intrusive. I think Jenkins needs a general-purpose notification system that the input step could hook into. (There is a system of administrative monitors, but restricted to administrators looking at the Manage Jenkins page.)

          It doesn't blink on the main Jenkins job list page. Further, if you restart Jenkins, the ball for paused jobs stops blinking

          If true, both smell like bugs. The ball for a job should match that of its latest build, which should be animated if the build is still in progress. I am pretty sure I have seen this all working in the past 24 hours, but there may be specific conditions you hit where this breaks. Anyway if you can reproduce from scratch please file separately to avoid distraction here.

          (Workflow 1.8+ does intentionally hide the “flyweight” executor from the master section of the executor widget when the build is paused, or indeed doing something in a step like sh but not actively running Groovy code. But this is unrelated to the build history widget and to ball colors.)

          Jesse Glick added a comment - Yes this is a long-discussed RFE. With the stage view (at job level) you do get a special badge on those build rows waiting for input, which could be made more prominent, but anyway we still need some mechanism (on a view page, perhaps) for showing you all builds of any job awaiting approval (ideally filtered by those you could actually approve, when submitter is specified). Adding a list view column is too intrusive. I think Jenkins needs a general-purpose notification system that the input step could hook into. (There is a system of administrative monitors, but restricted to administrators looking at the Manage Jenkins page.) It doesn't blink on the main Jenkins job list page. Further, if you restart Jenkins, the ball for paused jobs stops blinking If true, both smell like bugs. The ball for a job should match that of its latest build, which should be animated if the build is still in progress. I am pretty sure I have seen this all working in the past 24 hours, but there may be specific conditions you hit where this breaks. Anyway if you can reproduce from scratch please file separately to avoid distraction here. (Workflow 1.8+ does intentionally hide the “flyweight” executor from the master section of the executor widget when the build is paused, or indeed doing something in a step like sh but not actively running Groovy code. But this is unrelated to the build history widget and to ball colors.)
          Jesse Glick made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Jesse Glick made changes -
          Labels Original: workflow New: ux
          Kohsuke Kawaguchi made changes -
          Link New: This issue is related to JENKINS-31154 [ JENKINS-31154 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-32343 [ JENKINS-32343 ]

          Marc Esher added a comment -

          Big +1 on this. Right now, it's very hard to tell when something is waiting on input unless you know exactly what you're looking for. Making it more obvious / prominent would be a big UX win.

          Related, I had a job that kicked off, and we didn't know it was waiting on input. Several days later, the thing is still waiting, and then it wouldn't abort or proceed when we clicked the links, no matter how many times. The job would not cancel, either. The only thing that cleared out its cobwebs was a Jenkins restart.

          Marc Esher added a comment - Big +1 on this. Right now, it's very hard to tell when something is waiting on input unless you know exactly what you're looking for. Making it more obvious / prominent would be a big UX win. Related, I had a job that kicked off, and we didn't know it was waiting on input. Several days later, the thing is still waiting, and then it wouldn't abort or proceed when we clicked the links, no matter how many times. The job would not cancel, either. The only thing that cleared out its cobwebs was a Jenkins restart.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 166292 ] New: JNJira + In-Review [ 182342 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]
          Andrew Bayer made changes -
          Component/s Original: workflow-plugin [ 18820 ]

            jglick Jesse Glick
            owenmehegan Owen Mehegan
            Votes:
            10 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: