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

Hard to find "Click here to forcibly terminate running steps"

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • pipeline
    • 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.

          [JENKINS-32691] Hard to find "Click here to forcibly terminate running steps"

          Sorin Sbarnea added a comment -

          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.

          Sorin Sbarnea added a comment - 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.

          davidkarlsen added a comment -

          +1 - and if the jobs are deleted the links to add /term and /kill to will not be available.

          davidkarlsen added a comment - +1 - and if the jobs are deleted the links to add /term and /kill to will not be available.

            jglick Jesse Glick
            rodrigc Craig Rodrigues
            Votes:
            8 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: