-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
If I understand the abort stuck builds feature, it is intended to kill builds
that hang due to some sort of execution. However, builds are reported to be
stuck even if they are simply waiting their turn in the queue. It seems like
this timer should not start until the job begins execution.
- is duplicated by
-
JENKINS-3040 replace 'appears to be stuck' with an icon
-
- Closed
-
The intention of marking such jobs in the queue is to let you know that these
are starving for additional executors — it's time to add more slaves.
Perhaps we should change the wording a bit? Like from "stuck" to "starving
executors" or something like that? With perhaps a hyperlink to a page in Wiki
that talks about what you are supposed to do when you see it?
Or maybe we should change the color from red to something less scary, like yellow?