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

[TEP-0076]Validate Pipeline results array index #5139

Merged

Conversation

Yongxuanzhang
Copy link
Member

@Yongxuanzhang Yongxuanzhang commented Jul 14, 2022

Changes

This is part of work in TEP-0076.
Previous to this commit, we have added support for pipeline array
results indexing. This commit adds the validation to check if it is out
of bound.

Submitter Checklist

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

  • Has Docs included if any changes are user facing
  • 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
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

pipelinerun will fail if pipelineresults array index is out of bound

@tekton-robot
Copy link
Collaborator

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@tekton-robot tekton-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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. labels Jul 14, 2022
@Yongxuanzhang
Copy link
Member Author

/kind feature

@tekton-robot tekton-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 14, 2022
@Yongxuanzhang Yongxuanzhang force-pushed the validate-pipeline-array-results branch from a5f7a37 to a2370d4 Compare July 14, 2022 17:05
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. 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. labels Jul 14, 2022
@Yongxuanzhang Yongxuanzhang marked this pull request as ready for review July 14, 2022 17:06
@tekton-robot tekton-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 14, 2022
@tekton-robot tekton-robot requested a review from abayer July 14, 2022 17:06
@Yongxuanzhang
Copy link
Member Author

#4723

@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/resultref.go 100.0% 98.2% -1.8
pkg/reconciler/pipelinerun/resources/apply.go 98.8% 98.8% 0.0

This is part of work in TEP-0075.
Previous to this commit, we have added support for pipeline array
results indexing. This commit adds the validation to check if it is out
of bound.
@Yongxuanzhang Yongxuanzhang force-pushed the validate-pipeline-array-results branch from a2370d4 to 6c3c47e Compare July 14, 2022 17:12
@Yongxuanzhang
Copy link
Member Author

@ywluogg

@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/reconciler/pipelinerun/resources/apply.go 98.8% 98.8% 0.0

@Yongxuanzhang
Copy link
Member Author

/retest

@ywluogg
Copy link
Contributor

ywluogg commented Jul 14, 2022

/assign @ywluogg

@ywluogg
Copy link
Contributor

ywluogg commented Jul 14, 2022

This is mostly code split from #5088, so giving quick LGTM

@ywluogg
Copy link
Contributor

ywluogg commented Jul 14, 2022

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 14, 2022
@ywluogg
Copy link
Contributor

ywluogg commented Jul 14, 2022

#4723

@Yongxuanzhang
Copy link
Member Author

/retest

2 similar comments
@Yongxuanzhang
Copy link
Member Author

/retest

@Yongxuanzhang
Copy link
Member Author

/retest

@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/reconciler/pipelinerun/resources/apply.go 98.8% 98.8% 0.0

@Yongxuanzhang
Copy link
Member Author

/retest

@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 Jul 14, 2022
@Yongxuanzhang Yongxuanzhang changed the title [TEP-0075]Validate Pipeline results array index [TEP-0076]Validate Pipeline results array index Jul 14, 2022
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lbernick

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 Jul 14, 2022
@tekton-robot tekton-robot merged commit 895edb6 into tektoncd:main Jul 14, 2022
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/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. 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.

4 participants