-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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: Matrix - Minimal Status is Required #5019
Conversation
/lgtm |
Related PR: tektoncd/community#736 |
The following is the coverage report on the affected files.
|
[TEP-0090: Matrix][tep-0090] proposed executing a `PipelineTask` in parallel `TaskRuns` and `Runs` with substitutions from combinations of `Parameters` in a `Matrix`. The status of `PipelineRuns` with fanned-out `PipelineTasks` will list all the `TaskRuns` and `Runs` created. In [TEP-0100][tep-0100] we proposed changes to `PipelineRun` status to reduce the amount of information stored about the status of `TaskRuns` and `Runs` to improve performance, reduce memory bloat and improve extensibility. With the minimal `PipelineRun` status, we can handle `Matrix` without exacerbating the performance and storage issues that were there before. In this change, we validate that minimal embedded status is enabled when a `PipelineTask` has a `Matrix`. [tep-0090]: https://github.com/tektoncd/community/blob/main/teps/0090-matrix.md [tep-0100]: https://github.com/tektoncd/community/blob/main/teps/0100-embedded-taskruns-and-runs-status-in-pipelineruns.md
d6c142d
to
5d388a1
Compare
The following is the coverage report on the affected files.
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom 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 |
/kind feature |
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
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
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: #5019
Changes
TEP-0090: Matrix proposed executing a
PipelineTask
inparallel
TaskRuns
andRuns
with substitutions from combinationsof
Parameters
in aMatrix
.The status of
PipelineRuns
with fanned-outPipelineTasks
willlist all the
TaskRuns
andRuns
created.In TEP-0100 we proposed changes to
PipelineRun
statusto reduce the amount of information stored about the status of
TaskRuns
andRuns
to improve performance, reduce memory bloatand improve extensibility. With the minimal
PipelineRun
status,we can handle
Matrix
without exacerbating the performance andstorage issues that were there before.
In this change, we validate that minimal embedded status is enabled
when a
PipelineTask
has aMatrix
.Submitter Checklist
As the author of this PR, please check off the items in this checklist:
Release Notes