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

Add configuration to require confirmation to cancel job

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • 2.32.1 on Ubuntu

      Recently, core was updated to require confirmation when a running job is attempted to be cancelled or removed from the queue. JENKINS-30565

      I would like this to be controlled by a permission. Something along the lines of "requires cancel confirmation". The default value would be to require the confirmation which follows the existing behavior.

      In our environment, we would not require the administrative group to get this confirmation dialog.

      Use Case: Several jobs spawned automatically which need to be aborted rapidly. Not all jobs in the queue fall in this category at the time so purging the entire queue (which we have a scriptler to handle) is not appropriate.

          [JENKINS-41065] Add configuration to require confirmation to cancel job

          Daniel Beck added a comment -

          I do realize I'm taking the "my baby isn't ugly" position, but let me try being objective anyway

          we would not require the administrative group to get this confirmation dialog. Use Case: Several jobs spawned automatically which need to be aborted rapidly.

          Admins can always set Jenkins into quiet down mode for a minute to clean up from the queue, so this seems unnecessary.

          Something along the lines of "requires cancel confirmation". The default value would be to require the confirmation which follows the existing behavior.

          Not useful for this to require a permission. It's not about allowing (or not) to do something after all.

          The only useful approach I could think of would be to let users opt out of this protection from accidental clicks via an option on their user record (like case-insensitive search) – i.e. opting into getting yelled at for accidentally aborting a 20 hour build 18 hours in --, but I'd like to see a lot more demand for this before considering adding yet another checkbox.

          Daniel Beck added a comment - I do realize I'm taking the "my baby isn't ugly" position, but let me try being objective anyway we would not require the administrative group to get this confirmation dialog. Use Case: Several jobs spawned automatically which need to be aborted rapidly. Admins can always set Jenkins into quiet down mode for a minute to clean up from the queue, so this seems unnecessary. Something along the lines of "requires cancel confirmation". The default value would be to require the confirmation which follows the existing behavior. Not useful for this to require a permission . It's not about allowing (or not) to do something after all. The only useful approach I could think of would be to let users opt out of this protection from accidental clicks via an option on their user record (like case-insensitive search) – i.e. opting into getting yelled at for accidentally aborting a 20 hour build 18 hours in --, but I'd like to see a lot more demand for this before considering adding yet another checkbox.

          Jeff G added a comment -

          I appreciate your feedback on my request.

          I would be happy to have a global configuration which indicated if the confirmation is needed system wide. Our Jenkins is internally facing and we have user enforced (slap on the wrist) policies which make this new feature a burden for us.

          I do not think the individual user should be able to opt out if that's what you were hinting at. Your feature, for those environments which want to use it, should be on for all users which it is applicable.

          I completely understand your use case. I'm just asking for a way to opt out of the new functionality for some or all users. I also completely understand the overhead of adding yet another flag which needs to be maintained and validated repeatedly for functionality.

          Leverage the quiet mode is an extra step and then all the confirmations to be clicked subsequently... followed by removing quiet mode.

          In summary, not everyone requires or asked for the new feature. We should not all be subjected to it. Jenkins had been around a very long time without it and while there were likely asks, it was not a big enough ask for anyone to actually build it until now.

          Jeff G added a comment - I appreciate your feedback on my request. I would be happy to have a global configuration which indicated if the confirmation is needed system wide. Our Jenkins is internally facing and we have user enforced (slap on the wrist) policies which make this new feature a burden for us. I do not think the individual user should be able to opt out if that's what you were hinting at. Your feature, for those environments which want to use it, should be on for all users which it is applicable. I completely understand your use case. I'm just asking for a way to opt out of the new functionality for some or all users. I also completely understand the overhead of adding yet another flag which needs to be maintained and validated repeatedly for functionality. Leverage the quiet mode is an extra step and then all the confirmations to be clicked subsequently... followed by removing quiet mode. In summary, not everyone requires or asked for the new feature. We should not all be subjected to it. Jenkins had been around a very long time without it and while there were likely asks, it was not a big enough ask for anyone to actually build it until now.

            Unassigned Unassigned
            jgrant216 Jeff G
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: