-
Notifications
You must be signed in to change notification settings - Fork 136
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
Add new v2alpha4 version for TaskRuns #1111
Add new v2alpha4 version for TaskRuns #1111
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. |
d4c6dd2
to
aaab6d7
Compare
/ok-to-test |
aaab6d7
to
ad42c97
Compare
The following is the coverage report on the affected files.
|
/retest |
1 similar comment
/retest |
ad42c97
to
67726fe
Compare
67726fe
to
c4f3e41
Compare
The following is the coverage report on the affected files.
|
c4f3e41
to
cc88a97
Compare
The following is the coverage report on the affected files.
|
cc88a97
to
602ffcf
Compare
The following is the coverage report on the affected files.
|
/retest |
The following is the coverage report on the affected files.
|
35a0998
to
a1633e3
Compare
The following is the coverage report on the affected files.
|
2200ea4
to
ce90cb6
Compare
The following is the coverage report on the affected files.
|
ce90cb6
to
7f0127e
Compare
The following is the coverage report on the affected files.
|
e391065
to
fe57763
Compare
The following is the coverage report on the affected files.
|
fe57763
to
9339b2c
Compare
The following is the coverage report on the affected files.
|
9339b2c
to
46d1109
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 TaskRun. Also, the way chains read results from TaskRun 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 new `isBuildArtifact` property in the value
46d1109
to
89cd6c6
Compare
The following is the coverage report on the affected files.
|
89cd6c6
to
1611c11
Compare
The following is the coverage report on the affected files.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chitrangpatel, lcarva 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 |
Thanks for the linter fixes! |
Related with: #1065
This new version will now process the information from any associated StepAction from the executed TaskRun.
Also, the way chains read results from TaskRun 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 valueNOTE: Updating the Tekton version used in e2e tests to enable StepActions is breaking the Rekor behavior. A tracking issue was opened in #1117. After we solve that issue we would be able to add back the integration test with StepActions. We evaluated to do the test using the GitHub actions but we don't have an easy way to target an specific e2e test to not run in all the matrix of Pipeline releases. Also looks like GitHub tests are only testing one case.
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes