-
Notifications
You must be signed in to change notification settings - Fork 135
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
PipelineRuns with v2alpha4 to process StepActions #1118
PipelineRuns with v2alpha4 to process StepActions #1118
Conversation
Hi @renzodavid9. 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. |
12d8357
to
265c09d
Compare
0cbce63
to
9250178
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.
/ok-to-test
9250178
to
9a04b10
Compare
9a04b10
to
08fd75f
Compare
5d27a66
to
2586135
Compare
/retest |
The following is the coverage report on the affected files.
|
Please fix the linter errors and add a release note. |
2586135
to
6872bd3
Compare
The following is the coverage report on the affected files.
|
3522d9d
to
c79c0e1
Compare
The following is the coverage report on the affected files.
|
This new version will now process the information from any associated StepAction from the executed PipelineRun when `artifacts.pipelinerun.enable-deep-inspection` is set to `true`. Also, the way chains read results from PipelineRuns to populate the `subjects` field is changing: now the user has to explicitly mark a result as a subject using an object type-hinted tag (*ARTIFACT_OUTPUTS) + the new `isBuildArtifact` property in the value. Refactors to share logic between v2alph3 and v2alpha4.
c79c0e1
to
e72c6e7
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Thanks for the cleanup Renzo! Happy to approve after fixing the linter error. |
…hen two or more tasks/steps are using the same prefix.
7a1ee59
to
323779b
Compare
The following is the coverage report on the affected files.
|
/lgtm |
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 for you work on this Renzo! It wraps up support for StepResults as discussed in issue
#1065
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chitrangpatel 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 |
/retest |
This new version will now process the information from any associated StepAction from the executed PipelineRun.
Also, the way chains read results from PipelineRuns to populate the
subjects
field is changing: now the user has to explicitly mark a result as a subject using an bject type-hinted tag (*ARTIFACT_OUTPUTS) + the newisBuildArtifact
property in the value.Refactors to share logic between v2alph3 and v2alpha4.
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes