Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
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
- is related to
-
JENKINS-45592 Ability to disable the prompt when deleting queued build
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Remote Link | This issue links to "jenkins/pull/1835 (Web Link)" [ 13157 ] |
Workflow | JNJira [ 165677 ] | JNJira + In-Review [ 182084 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Rank | Ranked higher |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Link |
This issue is related to |
Probably the main issue that in highly active queue UI can send abort to wrong running job because of refresh rendering.