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

Cleanup: Remove "substituted context" task validation #6671

Merged
merged 1 commit into from
May 18, 2023

Conversation

lbernick
Copy link
Member

Prior to this commit, when a sentinel value was injected into the context, TaskSpec.Validate skipped most validation. This logic was introduced in #4835. However, there are no longer places in the codebase, other than tests, where this sentinel value was used. This commit removes this logic. No functional changes.

/kind cleanup

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • n/a Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Prior to this commit, when a sentinel value was injected into the context,
TaskSpec.Validate skipped most validation. However, there are no places in the codebase,
other than tests, where this sentinel value was used.
This commit removes this logic. No functional changes.
@tekton-robot tekton-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. release-note-none Denotes a PR that doesnt merit a release note. labels May 16, 2023
@tekton-robot tekton-robot requested review from abayer and jerop May 16, 2023 20:47
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 16, 2023
@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 16, 2023
@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/v1/task_validation.go 97.3% 97.3% -0.0
pkg/apis/pipeline/v1beta1/task_validation.go 97.3% 97.2% -0.0

@tekton-robot
Copy link
Collaborator

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

File Old Coverage New Coverage Delta
pkg/apis/pipeline/v1/task_validation.go 97.3% 97.3% -0.0
pkg/apis/pipeline/v1beta1/task_validation.go 97.3% 97.2% -0.0

@lbernick
Copy link
Member Author

It looks like all these test failures are actually flakes-- all are related to git clone failures that I think are transient and definitely aren't related to this PR. The alpha integration tests failed due to #6626.
/retest

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom, JeromeJu

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

@chitrangpatel
Copy link
Contributor

/retest

@chitrangpatel
Copy link
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 17, 2023
@lbernick
Copy link
Member Author

/retest

everything seems to be failures fetching/cloning git 🤔

@lbernick
Copy link
Member Author

/retest

I think things are working again based on the prow dashboard

@lbernick lbernick closed this May 18, 2023
@lbernick lbernick reopened this May 18, 2023
@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/v1/task_validation.go 97.3% 97.3% -0.0
pkg/apis/pipeline/v1beta1/task_validation.go 97.3% 97.2% -0.0

@lbernick
Copy link
Member Author

/retest

@lbernick lbernick closed this May 18, 2023
@lbernick lbernick reopened this May 18, 2023
@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/v1/task_validation.go 97.3% 97.3% -0.0
pkg/apis/pipeline/v1beta1/task_validation.go 97.3% 97.2% -0.0

@tekton-robot
Copy link
Collaborator

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

File Old Coverage New Coverage Delta
pkg/apis/pipeline/v1/task_validation.go 97.3% 97.3% -0.0
pkg/apis/pipeline/v1beta1/task_validation.go 97.3% 97.2% -0.0

@tekton-robot tekton-robot merged commit 59af0d9 into tektoncd:main May 18, 2023
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants