-
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 - Retries #5305
Conversation
The following is the coverage report on the affected files.
|
/retest |
/assign |
60bed43
to
c4ee5d7
Compare
The following is the coverage report on the affected files.
|
c4ee5d7
to
a9b4665
Compare
The following is the coverage report on the affected files.
|
a9b4665
to
75a1c00
Compare
The following is the coverage report on the affected files.
|
[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 |
[TEP-0090: Matrix][tep-0090] proposed executing a `PipelineTask` in parallel `TaskRuns` and `Runs` with substitutions from combinations of `Parameters` in a `Matrix`. Today, a matrixed `PipelineTask` that has retries will reattempt each matrixed `TaskRun` when one of them fails. In this change, we fix this issue such that each retry is completed for each matrixed `TaskRun`. That is, each retry for each `TaskRun` is completed before it is reattempted; failure in one matrixed `TaskRun` no longer affects retries for other matrixed `TaskRuns` from the same `PipelineTask`. [tep-0090]: https://github.com/tektoncd/community/blob/main/teps/0090-matrix.md
75a1c00
to
0ea2535
Compare
The following is the coverage report on the affected files.
|
/lgtm |
Changes
TEP-0090: Matrix proposed executing a
PipelineTask
in parallelTaskRuns
andRuns
with substitutions from combinations ofParameters
in aMatrix
.Today, a matrixed
PipelineTask
that has retries will reattempt each matrixedTaskRun
when one of them fails. In this change, we fix this issue such that each retry is completed for each matrixedTaskRun
. That is, each retry for eachTaskRun
is completed before it is reattempted; failure in one matrixedTaskRun
no longer affects retries for other matrixedTaskRuns
from the samePipelineTask
.Many thanks to @AlanGreene for catching this issue!
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes