-
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
Is there any way to tell whether any of the finally tasks failed? #3715
Comments
I believe there is a TEP in the work for this : In the meantime this gets discussed/implemented, I have done something like this to get slack notifications, the main code detection is here which returns the list of the failed tasks : You can get the current https://github.com/chmouel/tekton-asa-code/blob/47bd39d/README.md#L287-L290 Not straightforward, but hopefully the TEP would make all of this obsolete and easier to work with results. /kind question |
@riceluxs1t would tagging taskRun of |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
We do not have any solution to this yet. |
I have a pipeline that has
task1 -> task 2 -> ... -> taskN | singleFinallyTask.
When
singleFinallyTask
fails for whatever reasons, is there an easy way to usekubectl
ortkn
to tell?The text was updated successfully, but these errors were encountered: