Description

As a developer, I would like to navigate from a PipelineRun to the related TaskRuns and their associated pods so that I can debug my pipelines by looking at the volumes, secrets, etc that are made available to the taskruns and pods.

Acceptance criteria

• User has an experience similar to how pipeline page has a PipelineRun tab that lists the associated PipelineRuns, the PipelineRun page should have a TaskRuns tab that lists the associated TaskRuns.
  • The TaskRun list should at minimum contain the following information:
    • TaskRun resource name e.g. petclinic-deployment-pipeline-afj35c-build-image-8p7f8
    • TaskRun name in the pipeline e.g. build
    • Task name referenced by the TaskRun, if a Task is referenced
    • Pod name that executed the TaskRun with a link to the pod resource
    • TaskRun status (in case of failure, the error as a tooltip)
  • TaskRun Details
    • Task Run details page should have a Logs tab
    • The Details tab of the Task Run details page should show the status of the Task Run
    • If the Task Run is failed, it should show a snippet of the log in the status area
    • The header of the Task Run details page should include the status indicator
    • The Task Run details page should reference the Task Run pod and allow user to easily navigate to the pod details page

Problem:
When users want to debug pipelines, they need to dig deep in what is made available in the execution pods and currently there is no way to get to pods from a pipelinerun other than guessing the name of the pods in the admin console

Why is this important:
To facilitate debugging pipelines.

Dependencies (internal and external):
NA