-
Improvement
-
Resolution: Duplicate
-
Blocker
-
None
Hi,
I recently had a pipeline running, and had to terminate it from the web
interface by clicking on the red "X" icon.
The build did not terminate. At this point, I had to go to:
https://jenkins.freebsd.org/job/FreeBSD_HEAD/75/console
then I had to scroll all the way to the bottom, and click on:
Click here to forcibly terminate running steps
It took me a long time to figure out that this link even existed.
Can this link be put in a better place?
The current behavior is not intuitive at all from a UI perspective.
- duplicates
-
JENKINS-33721 Hard kill links could be in the build sidepanel
-
- Resolved
-
- is related to
-
JENKINS-28183 Hard killed job's stage blocks stage in following jobs
-
- Resolved
-
[JENKINS-32691] Hard to find "Click here to forcibly terminate running steps"
Priority | Original: Minor [ 4 ] | New: Blocker [ 1 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 168352 ] | New: JNJira + In-Review [ 198410 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Here is the idea, in certain conditions, this bug does block Jenkins completely, is persistent even system restarts and the affected job may not even have a console. It seems that is impossible to get rid of the blocked jobs and Jenkins doesn't do anything.