[JENKINS-30565] Jenkins should ask for confirmation before aborting a build

[jenkins-infra-bot]

Jenkins does not ask for confirmation before aborting a build. Since this can cause significant harm in the case of long-running builds or builds with side effects (partial deployments etc.), this should be added to the abort functionality.

Queued items can be parameterized or triggered in a way that makes them difficult to reproduce (actions added etc.) so those should probably be protected from accidentally canceling them as well.

---

Originally reported by danielbeck, imported from: Jenkins should ask for confirmation before aborting a build

• assignee: danielbeck
• status: Resolved
• priority: Minor
• component(s): core
• resolution: Fixed
• resolved: 2017-03-08T09:40:08+00:00
• votes: 3
• watchers: 6
• imported: 2025-11-24

Raw content of original issue

Jenkins does not ask for confirmation before aborting a build. Since this can cause significant harm in the case of long-running builds or builds with side effects (partial deployments etc.), this should be added to the abort functionality.

Queued items can be parameterized or triggered in a way that makes them difficult to reproduce (actions added etc.) so those should probably be protected from accidentally canceling them as well.

[jenkins-infra-bot]

• Remote link associated with this issue:

  • jenkins/pull/1835

[jenkins-infra-bot]

integer:

• Original comment link
• Raw content of original comment:

  Probably the main issue that in highly active queue UI can send abort to wrong running job because of refresh rendering.
  

Probably the main issue that in highly active queue UI can send abort to wrong running job because of refresh rendering.

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  True. Another reason for having this. That was actually the reason I went the extra inch and added the job name for queue items, and job name and build name for running builds, rather than just asking "Are you sure you want to abort?".
  

True. Another reason for having this. That was actually the reason I went the extra inch and added the job name for queue items, and job name and build name for running builds, rather than just asking "Are you sure you want to abort?".

[jenkins-infra-bot]

integer:

• Original comment link
• Raw content of original comment:

  Side effect is that if i mistakenly run build i want abort it very fast. And now i can do it. 
  

Side effect is that if i mistakenly run build i want abort it very fast. And now i can do it.

[jenkins-infra-bot]

scm_issue_link:

• Original comment link
• Raw content of original comment:

  Code changed in jenkins
  User: Daniel Beck
  Path:
   core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.properties
   core/src/main/resources/hudson/widgets/HistoryWidget/entry.jelly
   core/src/main/resources/hudson/widgets/HistoryWidget/entry.properties
   core/src/main/resources/lib/hudson/buildCaption.jelly
   core/src/main/resources/lib/hudson/buildCaption.properties
   core/src/main/resources/lib/hudson/executors.jelly
   core/src/main/resources/lib/hudson/executors.properties
   core/src/main/resources/lib/hudson/queue.jelly
   core/src/main/resources/lib/hudson/queue.properties
   core/src/main/resources/lib/layout/stopButton.jelly
  http://jenkins-ci.org/commit/jenkins/3af3a27116ccec048ce9eb61f947d74e0fe37611
  Log:
    [FIX JENKINS-30565] Ask for confirmation before canceling/aborting (#1835)
  
  
  

Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.properties
core/src/main/resources/hudson/widgets/HistoryWidget/entry.jelly
core/src/main/resources/hudson/widgets/HistoryWidget/entry.properties
core/src/main/resources/lib/hudson/buildCaption.jelly
core/src/main/resources/lib/hudson/buildCaption.properties
core/src/main/resources/lib/hudson/executors.jelly
core/src/main/resources/lib/hudson/executors.properties
core/src/main/resources/lib/hudson/queue.jelly
core/src/main/resources/lib/hudson/queue.properties
core/src/main/resources/lib/layout/stopButton.jelly
http://jenkins-ci.org/commit/jenkins/3af3a27116ccec048ce9eb61f947d74e0fe37611
Log:
[FIX JENKINS-30565] Ask for confirmation before canceling/aborting (#1835)

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  The fix has been released in 2.21
  

The fix has been released in 2.21

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  danielbeck Is it something we want to have in 2.19.x LTS?
  

danielbeck Is it something we want to have in 2.19.x LTS?

[jenkins-infra-bot]

splashnenen:

• Original comment link
• Raw content of original comment:

  HI,
  After installing Jenkins 2.21, we indeed have a confirmation message before canceling running job or deleting job from queue but when we check the box 'don't display this kind of message anymore' the message well doesn't display anymore but job cancelation has no effect.
  
  Job is well canceled or removed form queue only when we click on the confirmation message.
  Could you have a look on that please ? 
  Thx
  

HI,
After installing Jenkins 2.21, we indeed have a confirmation message before canceling running job or deleting job from queue but when we check the box 'don't display this kind of message anymore' the message well doesn't display anymore but job cancelation has no effect.

Job is well canceled or removed form queue only when we click on the confirmation message.
Could you have a look on that please ?
Thx

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  'don't display this kind of message anymore' the message well doesn't display anymore but job cancelation has no effect.
  
  Don't do that then. It's a browser feature designed to prevent popup spam. It won't magically remember your previous answer.
  
  oleg_nenashev No, not a backportable fix.
  

'don't display this kind of message anymore' the message well doesn't display anymore but job cancelation has no effect.

Don't do that then. It's a browser feature designed to prevent popup spam. It won't magically remember your previous answer.

oleg_nenashev No, not a backportable fix.

[jenkins-infra-bot]

ssides:

• Original comment link
• Raw content of original comment:

  "the message well doesn't display anymore but job cancelation has no effect"  hmmm...maybe you missed this point of the comment. 
  What I am currently looking at, I click the red x abort job button, a dialog comes up; I dismiss it; I click the red x again; another dialog comes up; I check that box and click ok. However, the job is not cancelled. Jenkins is still hung. The job cancellation has no effect and the jenkins ui is stuck, and the job will not be cancelled. I have to delete the job and/or restart jenkins. This is halfway through a pipeline job using 2.26.  
  

"the message well doesn't display anymore but job cancelation has no effect" hmmm...maybe you missed this point of the comment.
What I am currently looking at, I click the red x abort job button, a dialog comes up; I dismiss it; I click the red x again; another dialog comes up; I check that box and click ok. However, the job is not cancelled. Jenkins is still hung. The job cancellation has no effect and the jenkins ui is stuck, and the job will not be cancelled. I have to delete the job and/or restart jenkins. This is halfway through a pipeline job using 2.26.

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  "the message well doesn't display anymore but job cancelation has no effect" hmmm...maybe you missed this point of the comment.
  
  I did not. You told your browser "From now on, automatically reject all popup messages from this site", and that's what happens. Jenkins asks for confirmation, your browser tells it "No", and nothing gets cancelled. Remember, your computer does what you tell it to do, not what you want 
  
  The job cancellation has no effect and the jenkins ui is stuck, and the job will not be cancelled. I have to delete the job and/or restart jenkins.
  
  Or, you know, restart your browser to clear the flag you accidentally set.
  

"the message well doesn't display anymore but job cancelation has no effect" hmmm...maybe you missed this point of the comment.

I did not. You told your browser "From now on, automatically reject all popup messages from this site", and that's what happens. Jenkins asks for confirmation, your browser tells it "No", and nothing gets cancelled. Remember, your computer does what you tell it to do, not what you want

The job cancellation has no effect and the jenkins ui is stuck, and the job will not be cancelled. I have to delete the job and/or restart jenkins.

Or, you know, restart your browser to clear the flag you accidentally set.

[jenkins-infra-bot]

paulca:

• Original comment link
• Raw content of original comment:

  This should be feature switchable .... we have hundreds of automated tests that will eventually fail if a server is down. Once we know they're all going to fail we now have to click the popup to cancel each. Could we have an option in the Manage Jenkins menu to disable these popups ?
  

This should be feature switchable .... we have hundreds of automated tests that will eventually fail if a server is down. Once we know they're all going to fail we now have to click the popup to cancel each. Could we have an option in the Manage Jenkins menu to disable these popups ?

[jenkins-infra-bot]

paulca:

• Original comment link
• Raw content of original comment:

  This should really be switchable in the jenkins config
  

This should really be switchable in the jenkins config

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  > Could we have an option in the Manage Jenkins menu to disable these popups ?
  
  Likely it lies within the "feel free to contribute". If you have hundreds of tests, the best solution is to write a system Groovy script for it
  

> Could we have an option in the Manage Jenkins menu to disable these popups ?

Likely it lies within the "feel free to contribute". If you have hundreds of tests, the best solution is to write a system Groovy script for it

[jenkins-infra-bot]

paulca:

• Original comment link
• Raw content of original comment:

  Wouldn't that make upgrading more painful ? Having to remember to copy the groovy script etc ?  This was a feature requested by 1 person, with 2 additional votes, and it's made it straight into the main build. I suspect more people than just me will find it infuriating when they eventually upgrade.
  

Wouldn't that make upgrading more painful ? Having to remember to copy the groovy script etc ?  This was a feature requested by 1 person, with 2 additional votes, and it's made it straight into the main build. I suspect more people than just me will find it infuriating when they eventually upgrade.