-
Bug
-
Resolution: Fixed
-
Minor
-
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.
- is related to
-
JENKINS-45592 Ability to disable the prompt when deleting queued build
-
- Resolved
-
- links to
[JENKINS-30565] Jenkins should ask for confirmation before aborting a build
Remote Link | New: This issue links to "jenkins/pull/1835 (Web Link)" [ 13157 ] |
Workflow | Original: JNJira [ 165677 ] | New: JNJira + In-Review [ 182084 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Probably the main issue that in highly active queue UI can send abort to wrong running job because of refresh rendering.