Skip to content
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

Merged
merged 1 commit into from
Jun 8, 2022

Conversation

vsinghai
Copy link
Contributor

@vsinghai vsinghai commented Jun 6, 2022

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:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Release notes block below has been filled in
    (if there are no user facing changes, use release note "NONE")

Release Notes

Fixed a bug where static strings where not invalidated in `Pipeline Results`.

@tekton-robot tekton-robot requested a review from jerop June 6, 2022 18:55
@tekton-robot tekton-robot added kind/bug Categorizes issue or PR as related to a bug. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 6, 2022
@tekton-robot
Copy link
Collaborator

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

Copy link
Member

@jerop jerop left a 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

pkg/apis/pipeline/v1beta1/pipeline_validation_test.go Outdated Show resolved Hide resolved
@tekton-robot
Copy link
Collaborator

@jerop: cat image

In response to this:

welcome @vsinghai 🎉
/meow

/ok-to-test

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.

@tekton-robot tekton-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 6, 2022
@jerop
Copy link
Member

jerop commented Jun 6, 2022

@vsinghai please do the following:

@vsinghai vsinghai changed the title Pipeline Validation for Task Result expression in Pipeline Result Jun 6, 2022
@jerop jerop changed the title Validation for Task Result expression in Pipeline Result Validation for Task Result expressions in Pipeline Result Jun 6, 2022
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. release-note-none Denotes a PR that doesnt merit a release note. labels Jun 6, 2022
@jerop jerop removed the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Jun 7, 2022
@jerop
Copy link
Member

jerop commented Jun 7, 2022

@vsinghai this solution fixes part of bug #4922 - addresses initialized-2 but not initialized-3 - just wanted to confirm that it'd addressed separately (prefer the smaller PR anyway)

  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

@tekton-robot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. release-note-none Denotes a PR that doesnt merit a release note. labels Jun 7, 2022
@dibyom
Copy link
Member

dibyom commented Jun 7, 2022

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)
@dibyom
Copy link
Member

dibyom commented Jun 8, 2022

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2022
@pritidesai
Copy link
Member

@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 🙏

@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesnt merit a release note. labels Jun 8, 2022
@jerop
Copy link
Member

jerop commented Jun 8, 2022

/test pull-tekton-pipeline-alpha-integration-tests

@tekton-robot tekton-robot merged commit ad9e9dd into tektoncd:main Jun 8, 2022
@vsinghai vsinghai deleted the pipeline branch June 9, 2022 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants