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-0090: Refactor execution status validation #4635

Merged
merged 1 commit into from
Mar 1, 2022

Conversation

jerop
Copy link
Member

@jerop jerop commented Mar 1, 2022

Changes

Today, the execution status validation is long and has duplicated code. We need to validate execution status in matrix, a feature proposed in TEP-0090. To set up for that, we are refactoring the execution status validation in this change which includes splitting up the function and reusing common logic.

cc @pritidesai

Submitter Checklist

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

  • [n/a] 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 or deleted (only if no user facing changes)

Release Notes

NONE

@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. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 1, 2022
@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/pipeline_types.go 94.9% 96.1% 1.2

Today, the execution status validation is long and has duplicated
code. We need to validate execution status in matrix, a feature
proposed in TEP-0090. To set up for that, we are refactoring the
execution status validation in this change which includes splitting
up the function and reusing common logic.
@jerop jerop marked this pull request as ready for review March 1, 2022 18:23
@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 Mar 1, 2022
@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/pipeline_types.go 94.9% 96.1% 1.2

@jerop jerop added this to the Pipelines v0.34 milestone Mar 1, 2022
Copy link
Member

@pritidesai pritidesai left a comment

Choose a reason for hiding this comment

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

thank you @jerop

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pritidesai

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 Mar 1, 2022
@ghost
Copy link

ghost commented Mar 1, 2022

/lgtm

@tekton-robot tekton-robot assigned ghost Mar 1, 2022
@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 1, 2022
@jerop
Copy link
Member Author

jerop commented Mar 1, 2022

TestSidecarTaskSupport is a known flake: #2656

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

@tekton-robot tekton-robot merged commit b145b54 into tektoncd:main Mar 1, 2022
@jerop jerop deleted the tep-0090-validation-3 branch June 11, 2022 01:46
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. 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/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.

None yet

3 participants