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

Jenkins should ask for confirmation before aborting a build

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None

      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-30565] Jenkins should ask for confirmation before aborting a build

          Paul Carr added a 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 ?

          Paul Carr added a 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 ?

          Paul Carr added a comment -

          This should really be switchable in the jenkins config

          Paul Carr added a comment - This should really be switchable in the jenkins config

          Oleg Nenashev added a 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

          Oleg Nenashev added a 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

          Paul Carr added a 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.

          Paul Carr added a 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.

          Daniel Beck added a comment -

          This is resolved, anything else is a followup RFE.

          Daniel Beck added a comment - This is resolved, anything else is a followup RFE.

          Paul Carr added a comment -

          OK.

          Paul Carr added a comment - OK.

          Requiring all cancelled jobs to be acknowledge is ridiculous without being able to turn it off as a configuration setting.  I regularly have to cancel lots of running jobs. 

          Please add a configuration setting or pull this back.

          Eric Waltersdorf added a comment - Requiring all cancelled jobs to be acknowledge is ridiculous without being able to turn it off as a configuration setting.  I regularly have to cancel lots of running jobs.  Please add a configuration setting or pull this back.

          Daniel Beck added a comment -

          ewalt72 Again,

          This is resolved, anything else is a followup RFE.

          Please file that, and link it from here, if you feel something like that is necessary. Also, provide your use case. From my POV "I regularly have dozens or hundreds of builds in the queue and need to cancel them quickly" rather indicates a much different underlying problem to me. Stack Overflow calls this the "X/Y problem", maybe an entirely different solution would be more practical.

          Daniel Beck added a comment - ewalt72 Again, This is resolved, anything else is a followup RFE. Please file that, and link it from here, if you feel something like that is necessary. Also, provide your use case. From my POV "I regularly have dozens or hundreds of builds in the queue and need to cancel them quickly" rather indicates a much different underlying problem to me. Stack Overflow calls this the "X/Y problem", maybe an entirely different solution would be more practical.

          Oleg Nenashev added a comment - - edited

          If somebody wants to disable this feature, it is pretty trivial to do so by adding a SystemProperty to Jenkins. By default Jenkins should require confirmation IMHO

          Oleg Nenashev added a comment - - edited If somebody wants to disable this feature, it is pretty trivial to do so by adding a SystemProperty to Jenkins. By default Jenkins should require confirmation IMHO

          Daniel Beck added a comment -

          pretty trivial to do so

          Let's please not add new options without having determined whether there's an actual need for it. See my preceding comment.

          Daniel Beck added a comment - pretty trivial to do so Let's please not add new options without having determined whether there's an actual need for it. See my preceding comment.

            danielbeck Daniel Beck
            danielbeck Daniel Beck
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: