-
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
Validation for Task Result expressions in Pipeline Result #4941
Conversation
Hi @vsinghai. 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. |
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.
welcome @vsinghai 🎉
/meow
/ok-to-test
In response to this:
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. |
@vsinghai please do the following:
|
@vsinghai this solution fixes part of bug #4922 - addresses results:
- name: initialized-1
value: $(tasks.check-git-commit.results.init)
- name: initialized-2
value: this is static
- name: initialized-3
value: $(foo.bar) /approve |
[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 |
one tiny nit, otherwise looks good! |
Prior to this commit, the validation for static strings for Task Result expressions in Pipeline Results was not extensive. This commit adds the case where a pipeline would be invalid if there is no expression following the valid form `$(tasks.<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [tektoncd#4922](tektoncd#4922)
/lgtm |
@vsinghai thank you for this 👍 Welcome to the community 🎉 Please update the release notes since this is fixing a bug and will be very beneficial to the users consuming these changes 🙏 |
/test pull-tekton-pipeline-alpha-integration-tests |
Changes
Prior to this commit, the validation for static strings for Task Result expressions in Pipeline Results was not extensive.
This commit adds the case where a pipeline would be invalid if there is no expression following the valid form
$(tasks.<task-name>.results.<result-name>)
.Please reference this doc for more information.
Fixes bug #4922
/kind bug
/cc @jerop
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