Add a SKIPPED result status for stages#147
Merged
Merged
Conversation
Contributor
Author
|
Fix for #146 |
Contributor
|
This is great. Thanks. |
Contributor
Author
|
Test failure is a windows flake on the jenkins-owned CI. Confirmed working as expected in a lab. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A bit tricky what's going on here.
First Jenkins on its own does not differentiate in the UI a failed stage in a pipeline from a stage that has been skipped because of an earlier failure.
For example in this job, only the first stage failed but all the others are marked as failed:
While that's how jobs status are stored by Jenkins, BlueOcean is able to mark those other jobs as "skipped", see:

Currently skipped jobs are marked as failed in Datadog, this PR introduces a new tag value "result:SKIPPED" for those jobs