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

Refactor Pipeline Parameters Validation #3167

Merged
merged 1 commit into from Sep 3, 2020

Conversation

jerop
Copy link
Member

@jerop jerop commented Sep 3, 2020

Changes

Pipeline parameters were previously only used in task parameters. We need to use pipeline parameters in when expressions.

We're refactoring pipeline parameters validation so that we can easily add validation for parameters in when expressions.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

    NONE

/cc @bobcatfish @pritidesai

Currently, pipeline parameters are only used in task parameters. we need
to use Pipeline Parameters in When Expressions as well. Trying to add the
new validation became ugly, so we're refactoring parameters validation so '
that we can easily add validation for parameters in when expressions.
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Sep 3, 2020
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/pipeline/v1beta1/param_types.go 78.3% 78.0% -0.2
pkg/apis/pipeline/v1beta1/pipeline_validation.go 96.1% 97.2% 1.2

Copy link
Collaborator

@bobcatfish bobcatfish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!! Thanks for breaking this out. I think this is a lot clearer as several larger functions than the one line wrapper functions we had before

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bobcatfish

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 3, 2020
@bobcatfish bobcatfish added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Sep 3, 2020
@dibyom
Copy link
Member

dibyom commented Sep 3, 2020

/test check-pr-has-kind-label

@dibyom dibyom added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Sep 3, 2020
@jerop
Copy link
Member Author

jerop commented Sep 3, 2020

/test check-pr-has-kind-label

@dibyom dibyom added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Sep 3, 2020
@tekton-robot tekton-robot merged commit 9bc3fd8 into tektoncd:master Sep 3, 2020
@jerop jerop deleted the refactor-pipeline-validation branch September 30, 2020 16:00
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/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. 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.

None yet

4 participants