-
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
WIP - implementing pipeline level finally #2651
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR cannot be merged: expecting exactly one kind/ label Available
|
2 similar comments
This PR cannot be merged: expecting exactly one kind/ label Available
|
This PR cannot be merged: expecting exactly one kind/ label Available
|
The following is the coverage report on the affected files.
|
/kind feature |
bab4c27
to
f75dff1
Compare
The following is the coverage report on the affected files.
|
f75dff1
to
f62c998
Compare
The following is the coverage report on the affected files.
|
f62c998
to
71ea79d
Compare
The following is the coverage report on the affected files.
|
71ea79d
to
7c4b81c
Compare
The following is the coverage report on the affected files.
|
7c4b81c
to
4327cd1
Compare
The following is the coverage report on the affected files.
|
4327cd1
to
d9a8784
Compare
The following is the coverage report on the affected files.
|
d9a8784
to
0c466e7
Compare
The following is the coverage report on the affected files.
|
0c466e7
to
41e5a0e
Compare
The following is the coverage report on the affected files.
|
We can now specify a list of tasks needs to be executed just before pipeline exits (either after finishing all non-final tasks successfully or after a single failure) Most useful for tasks such as report test results, cleanup cluster resources, etc ``` apiVersion: tekton.dev/v1beta1 kind: Pipeline metadata: name: pipeline-with-final-tasks spec: tasks: - name: pre-work taskRef: Name: some-pre-work - name: unit-test taskRef: Name: run-unit-test runAfter: - pre-work - name: integration-test taskRef: Name: run-integration-test runAfter: - unit-test finally: - name: cleanup-test taskRef: Name: cleanup-cluster - name: report-results taskRef: Name: report-test-results ```
41e5a0e
to
b26f852
Compare
@pritidesai: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Messed up resolving conflicts, opened a new PR #2661 😭 |
Changes
We can now specify a list of tasks needs to be executed just before
pipeline exits (either after finishing all non-final tasks successfully or after
a single failure)
Most useful for tasks such as report test results, cleanup cluster resources, etc
Design doc: https://docs.google.com/document/d/1lxpYQHppiWOxsn4arqbwAFDo4T0-LCqpNa6p-TJdHrw/edit#
Part of #1684
Fixes #2446
Depends on: #2650
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Users can now specify Tasks within a Pipeline that will always execute, even if Tasks fail, via the new `finally` clause