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: Get Names of TaskRuns from ChildReferences only #5036

Merged
merged 1 commit into from
Jun 24, 2022

Conversation

jerop
Copy link
Member

@jerop jerop commented Jun 24, 2022

Changes

In tektoncd/community#736, we decided that Matrix will use ChildReferences only. Therefore, it is unnecessary to check the TaskRuns field of PipelineRun status when getting the names of TaskRuns for matrixed PipelineTasks.

Related PRs: #5019, #4958

/kind cleanup

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 (if there are no user facing changes, use release note "NONE")

Release Notes

NONE

In tektoncd/community#736, we decided that
`Matrix` will use `ChildReferences` only. Therefore, it is unnecessary
to check the `TaskRuns` field of `PipelineRun` status when getting the
names of `TaskRuns` for matrixed `PipelineTasks`.

Related PR: tektoncd#5019
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 24, 2022
@jerop jerop changed the title Get Names of TaskRuns from ChildReferences only TEP-0090: Get Names of TaskRuns from ChildReferences only Jun 24, 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/reconciler/pipelinerun/resources/pipelinerunresolution.go 94.1% 94.0% -0.2

@jerop
Copy link
Member Author

jerop commented Jun 24, 2022

@abayer @dibyom please take a look

@abayer
Copy link
Contributor

abayer commented Jun 24, 2022

/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer

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 Jun 24, 2022
@dibyom
Copy link
Member

dibyom commented Jun 24, 2022

/lgtm

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

jerop commented Jun 24, 2022

/test pull-tekton-pipeline-integration-tests

@jerop
Copy link
Member Author

jerop commented Jun 24, 2022

/test pull-tekton-pipeline-build-tests

@tekton-robot tekton-robot merged commit 8330224 into tektoncd:main Jun 24, 2022
@jerop jerop deleted the matrix-uses-minimal-status-only branch June 24, 2022 22:23
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.

4 participants