-
Task
-
Resolution: Fixed
-
Major
-
None
-
-
atlantic, indian, iapetus
In Scope
- Ensure that API for steps, stages and parallels reflects the "aborted" state when a step is aborted
- When the Pipeline is aborted the stage & parallels shows up as failed. The stages & parallels should show up as aborted.
- When the Pipeline is aborted the executing steps show up as failed. The steps should show up as aborted.
- One this is completed, test that this works in the UI. If it does not work open a GUI ticket for updating it to handle the ABORTED state correctly.
Notes
svanoort has provided some technical details
Note that at least for stage, there is no result set. I aborted a build (kzantow/failure-project "passing" branch) and I saw the following:
{
"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl",
"_links": {},
"actions": [],
"displayName": "Archive",
"durationInMillis": 0,
"id": "9",
"result": null,
"startTime": null,
"state": null,
"edges": []
}
Which is not correct.
- blocks
-
JENKINS-38526 "General Build Step" and pipeline node icon don't reflect unstable results
-
- Closed
-
[JENKINS-38529] API Steps, stages and parallels should reflect the "aborted"
Sam Van Oort
added a comment - jamesdumay For Blue Ocean's purposes, assume that FlowNodes can individually be unstable, in the Bismuth outputs (although it's not common currently).
Sam Van Oort
added a comment - jamesdumay For Blue Ocean's purposes, assume that FlowNodes can individually be unstable, in the Bismuth outputs (although it's not common currently). Note: I think this might be done - just need to check aborted is ok (separate ticket for known problems with unstable)
jamesdumay this is still a prblem with aborted (I updated ticket). Unstable has another ticket to make it behave correctly so changed scope.
IF this requires some deeper changes to pipeline, we probably will punt this to another sprint (please do investigate if this is a small or a big change)
svanoort similar question as before - can flow nodes be marked "unstable"?