-
Notifications
You must be signed in to change notification settings - Fork 221
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 - Status #725
Conversation
cc @abayer @dibyom @lbernick @pritidesai please take a look |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abayer, dibyom, 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 |
API WG 6/13 |
[TEP-0090: Matrix][tep-0090] proposed executing a `PipelineTask` in parallel `TaskRuns` and `Runs` with substitutions from combinations of `Parameters` in a `Matrix`. In this change, we describe how the status of a `PipelineRun` with a matrixed `PipelineTask` would be in full and minimal modes. Previously, we had included `matrixId` to the `PipelineRun` status so that it can help with identifying `Results` from fanned out `TaskRuns` or `Runs`. However, we ended up descoping that problem so that it can be addressed when TEP-0075 and TEP-0076 are implemented. See [`Results` from fanned-out `PipelineTasks`][results] for details. In this change, we remove the `matrixId` in `PipelineRun` status so that the problem can be addressed completely later. [tep-0090]: https://github.com/tektoncd/community/blob/main/teps/0090-matrix.md [results]: https://github.com/tektoncd/community/blob/main/teps/0090-matrix.md#results-from-fanned-out-pipelinetasks
/lgtm |
TEP-0090: Matrix proposed executing a
PipelineTask
inparallel
TaskRuns
andRuns
with substitutions from combinationsof
Parameters
in aMatrix
.In this change, we describe how the status of a
PipelineRun
witha matrixed
PipelineTask
would be in full and minimal modes.Previously, we had included
matrixId
to thePipelineRun
statusso that it can help with identifying
Results
from fanned outTaskRuns
orRuns
. However, we ended up descoping that problemso that it can be addressed when TEP-0075 and TEP-0076 are implemented.
See
Results
from fanned-outPipelineTasks
for details.In this change, we remove the
matrixId
inPipelineRun
status sothat the problem can be addressed completely later.
/kind tep