-
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-0142: Introduce Value in TaskResults #7347
TEP-0142: Introduce Value in TaskResults #7347
Conversation
37ff8ec
to
9aea50f
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
9aea50f
to
0ec4fec
Compare
0ec4fec
to
bd859fd
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.
Thanks! Some minor comments, questions
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Yongxuanzhang 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 |
I think we need to fix alpha integration tests. It's because we enable step action for all alpha tests. And the tests are asserting the resolved results. But we are adding default string type for them |
bd859fd
to
caeda0c
Compare
This PR introduces the field `Value` in `TaskResults`. This field is necessary to capture the results produced by `StepActions` if the Task needs to resolve name conflicts. This is part of issue tektoncd#7259. Following this PR, we will add support for extracting StepAction results via termination message and sidecar logs.
caeda0c
to
54bda50
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
This PR introduces the field
Value
inTaskResults
. This field is necessary to capture the results produced byStepActions
if the Task needs to resolve name conflicts.This is part of issue #7259. Following this PR, we will add support for extracting StepAction results via termination message and sidecar logs.
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes
/kind feature