-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TEP-0103: Skipping Reason - Add SkippingReason to SkippedTasks field of PipelineRunStatus #4829
TEP-0103: Skipping Reason - Add SkippingReason to SkippedTasks field of PipelineRunStatus #4829
Conversation
Hi @chitrangpatel. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
SkippedTasks
field of PipelineRunStatus
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @chitrangpatel - left a few comments, please update the commit message (the first two paragraphs should be enough)
637a675
to
73f9295
Compare
Done! |
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @chitrangpatel!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
a8e133b
to
dbdfe63
Compare
/retest |
…tatus`. Today, users only know that a PipelineTask was skipped, but they don't know for which exact reason. This can be confusing when debugging Pipelines. In this PR, we add the reason for skipping to the SkippedTasks field in PipelineRunStatus to improve usability and debuggability. This commit adds a field `Reason` of type [`SkippingReason`][reasons] (a string alias) to the [`SkippedTasks`][skipped-tasks] field in `PipelineRunStatus`.
dbdfe63
to
a02fa96
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest |
TEP-0103: Skipping Reason : Add SkippingReason to SkippedTasks field of PipelineRunStatus.
Today, users only know that a PipelineTask was skipped, but they don't know for which exact reason.
This can be confusing when debugging Pipelines. In this PR, we add the reason for skipping to the
SkippedTasks field in PipelineRunStatus to improve usability and debuggability.
Changes
This commit adds a field
Reason
of typeSkippingReason
(a string alias) to theSkippedTasks
field inPipelineRunStatus
.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