-
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: Failure Strategies - Remove Fail Fast #4972
Conversation
The following is the coverage report on the affected files.
|
ff763e9
to
f079300
Compare
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I think this can be merged once Lee's comment is addressed
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
In tektoncd#4951, we implemented `isFailure` for matrixed `TaskRuns` where we applied fail-fast failure strategy. We discussed failure strategies further in this PR - tektoncd/community#724 - and API WG on 13 June 2022. We agreed to leave early termination upon failure out of scope for the initial release of Matrix. We plan to explore failure strategies, including fail-fast, in future work. And these failure strategies may apply more broadly beyond Matrix. In this change, we update `isFailure` to evaluate to `true` only when there's a failure and there are no running `TaskRuns` in the `rprt`.
f079300
to
10aa981
Compare
/lgtm |
/test tekton-pipeline-unit-tests |
/test pull-tekton-pipeline-go-coverage |
The following is the coverage report on the affected files.
|
Changes
In #4951, we implemented
isFailure
for matrixedTaskRuns
where we applied fail-fast failure strategy. We discussed failure strategies further in this PR - tektoncd/community#724 - and API WG on 13 June 2022. We agreed to leave early termination upon failure out of scope for the initial release of Matrix. We plan to explore failure strategies, including fail-fast, in future work. And these failure strategies may apply more broadly beyond Matrix.In this change, we update
isFailure
to evaluate totrue
only when there's a failure and there are no runningTaskRuns
in therprt
./kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
Release Notes