Is there any way to tell whether any of the finally tasks failed?

[riceluxs1t]

I have a pipeline that has
task1 -> task 2 -> ... -> taskN | singleFinallyTask.

When singleFinallyTask fails for whatever reasons, is there an easy way to use kubectl or tkn to tell?

[chmouel]

I believe there is a TEP in the work for this :

tektoncd/community#240

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 :

https://github.com/chmouel/tekton-asa-code/blob/47bd39d/misc/send-slack-notifications.py#L37-L57

You can get the current pipelinerun that is executing in a environement variable of a task like this :

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

[pritidesai]

@riceluxs1t would tagging taskRun of singleFinallyTask help your use case? We could classify taskRun created for finally tasks by adding a label to it. (something similar to #3721).

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[pritidesai]

We do not have any solution to this yet.
/lifecycle frozen