Should PipelineRun describe list the Task in addition (or with) the TaskRun

[vdemeester]

Currently, tkn pipelinerun describe my-run display the TaskRun attached to the PipelineRun.

This means:

• The list varies depending on the status of the PipelineRun as it only display the TaskRun that have been created.
• If the PipelineRun, there is no way to see how many Task(s) succeeded before the failure.

I think we should show the Pipeline Task for the PipelineRun, either merged with the TaskRun part (aka, listing the Task and attaching the TaskRun status to it) or in a separate table

/kind question

cc @siamaksade

[siamaksade]

Also related tektoncd/pipeline#994

It makes sense to show the tasks and attach their task runs

[vdemeester]

/kind feature
/remove-kind question

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

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.