Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
-
workflow-durable-task-step 2.24
Description
When a workflow is manually aborted in Jenkins it fires a hudson.AbortException. This is the same thing that happens when a step fails. Thus, it's impossible to properly set the build status to ABORTED on a manual abort and to FAILED on a failed step because you can't programmatically tell the difference.
jglick’s recommended fix: see comment as of 2017-06-28
Attachments
Issue Links
- is duplicated by
-
JENKINS-41944 Unable to understand when AbortError is created by user`s action like pressing button Stop
-
- Resolved
-
-
JENKINS-34376 Cannot easily/safely catch exceptions without disrupting job abortion
-
- Resolved
-
-
JENKINS-37724 Record cause of interruption in DurableTaskStep
-
- Resolved
-
- relates to
-
JENKINS-51928 Timeout is caught by the most internal try-catch, but should be caught by the try-catch that surrounds the timeout step
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Resolution | Cannot Reproduce [ 5 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Cannot Reproduce [ 5 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Summary | Can't distinguish between manual abort and failure in workflow plugin | Can't distinguish between durable task abort and failure in workflow plugin |
Workflow | JNJira [ 163682 ] | JNJira + In-Review [ 186290 ] |
Component/s | pipeline-general [ 21692 ] |
Component/s | workflow-plugin [ 18820 ] |
Component/s | workflow-durable-task-step-plugin [ 21715 ] | |
Component/s | pipeline [ 21692 ] |
Link |
This issue is duplicated by |
Link |
This issue is duplicated by |
Epic Link | JENKINS-35396 [ 171189 ] |
Link |
This issue is duplicated by |
Description | When a workflow is manually aborted in Jenkins it fires a hudson.AbortException. This is the same thing that happens when a step fails. Thus, it's impossible to properly set the build status to ABORTED on a manual abort and to FAILED on a failed step because you can't programmatically tell the difference. |
When a workflow is manually aborted in Jenkins it fires a hudson.AbortException. This is the same thing that happens when a step fails. Thus, it's impossible to properly set the build status to ABORTED on a manual abort and to FAILED on a failed step because you can't programmatically tell the difference. [~jglick]’s recommended fix: see comment as of 2017-06-28 |
Assignee | Jesse Glick [ jglick ] | Devin Nusbaum [ dnusbaum ] |
Status | Reopened [ 4 ] | Open [ 1 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "jenkinsci/workflow-durable-task-step-plugin#75 (Web Link)" [ 21823 ] |
Released As | workflow-durable-task-step 2.24 | |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Link |
This issue relates to |
Epic Link | JENKINS-35396 [ 171189 ] |