-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
pipeline-graph-analysis 1.9
Jenkins ver. 2.150.1
This issue is a knock-on from https://github.com/jenkinsci/pipeline-graph-analysis-plugin/commit/20e4807f35be96ea07a9c66d4238edf75705e4b5.
In our scripted pipelines we throw FlowInterruptedExceptions to set the Stage status. After upgrading from 1.7 to 1.9, stages in this context are now being marked Aborted. Previously the stages were marked as Failure.
- relates to
-
JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses
-
- Resolved
-
[JENKINS-55255] FlowInterruptedException always marks stages as Aborted despite Result
Description | Original: This issue is a knock-on from https://github.com/jenkinsci/pipeline-graph-analysis-plugin/commit/20e4807f35be96ea07a9c66d4238edf75705e4b5. |
New:
This issue is a knock-on from [https://github.com/jenkinsci/pipeline-graph-analysis-plugin/commit/20e4807f35be96ea07a9c66d4238edf75705e4b5]. In our scripted pipelines we throw FlowInterruptedExceptions to set the Stage status. After upgrading from 1.7 to 1.9, stages in this context are now being marked Aborted. Previously the stages were marked as Failure. |
Assignee | Original: Sam Van Oort [ svanoort ] | New: Stuart Rowe [ stuartrowe ] |
Link |
New:
This issue relates to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Released As | New: https://github.com/jenkinsci/pipeline-graph-analysis-plugin/releases/tag/pipeline-graph-analysis-1.10 | |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |