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

Jenkins should ask for confirmation before aborting a build

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            danielbeck 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 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.
            oleg_nenashev 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 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
            danielbeck 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.

            danielbeck 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.

            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.

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

            OK.

            paulca Paul Carr added a comment - OK.

            People

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

              Dates

                Created:
                Updated:
                Resolved: