Skip to content
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

"Finally" tasks for Pipeline #2446

Closed
dibyom opened this issue Apr 20, 2020 · 0 comments · Fixed by #2661
Closed

"Finally" tasks for Pipeline #2446

dibyom opened this issue Apr 20, 2020 · 0 comments · Fixed by #2661
Labels
area/api Indicates an issue or PR that deals with the API. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@dibyom
Copy link
Member

dibyom commented Apr 20, 2020

Expected Behavior

A Pipeline can specify tasks that always run at the end of a pipeline even if a task in the pipeline fails.

See design doc for syntax: https://docs.google.com/document/d/1lxpYQHppiWOxsn4arqbwAFDo4T0-LCqpNa6p-TJdHrw/edit

Larger context around failure handling design: #1684 (comment)

Additional Info

Part of #1684

/kind feature
/area api

@tekton-robot tekton-robot added kind/feature Categorizes issue or PR as related to a new feature. area/api Indicates an issue or PR that deals with the API. labels Apr 20, 2020
@dibyom dibyom added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Indicates an issue or PR that deals with the API. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
4 participants