Added SkippingReason field in the SkippedTasks
field of PipelineRunStatus
.
#1
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.
To address the TEP and issue.
Skipping Reason included in the
SkippedTasks
field ofPipelineRunStatus
.Prior to this, users only knew that a
PipelineTask
was skipped but notthe exact reason for skipping the task leading to confusion when
debugging
Pipelines
.This commit adds a field
Reason
of typeSkippingReason
(a string alias) to theSkippedTasks
field inPipelineRunStatus
. The tests have been updated to validate skipping reason.Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes