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.)
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.)
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.)