Story (Required)

As an OpenShift user trying to run complex automation workflows, I want the OpenShift Console UI to support visualizing and managing Pipelines that contain other Pipelines, so that I can effectively monitor and interact with these nested workflows once the feature graduates from alpha.

This story prepares the OpenShift Console UI to fully support the Pipelines-in-Pipelines feature as it advances to Beta, ensuring a consistent and functional user experience for managing nested Tekton resources.

Background (Required)

The Tekton project has introduced the concept of "Pipelines-in-Pipelines," allowing a Pipeline resource to execute another Pipeline resource as a task within it. This feature is currently in alpha but is expected to graduate to Beta. The UI needs to be updated to correctly display and interact with these nested pipeline structures to maintain usability for users leveraging this advanced functionality. See the official documentation here: https://github.com/tektoncd/pipeline/blob/main/docs/pipelines-in-pipelines.md

Out of scope

• Implementing any complex custom logic for nested pipeline execution within the Console backend/frontend.
• Modifying the behavior of existing non-nested pipeline visualization components.
• Supporting dynamic or conditional nesting (focusing on static nested pipeline calls for now).

Approach (Required)

The approach involves updating the relevant components in the OpenShift Console responsible for visualizing Tekton Pipelines to correctly interpret and render Task resources that reference another Pipeline. This includes ensuring that drill-down functionality or detail views correctly reflect the nested structure.

Dependencies

• Completion or sufficient stability of the underlying OpenShift/Tekton Pipelines-in-Pipelines API support.

Acceptance Criteria (Mandatory)

• The UI successfully displays a Pipeline that contains a task type configured as a nested Pipeline.
• When viewing the details of a running PipelineRun that utilizes Pipelines-in-Pipelines, the relationship between the parent and nested pipelines is visually represented correctly.
• Navigation or drill-down actions from the parent PipelineRun view to the nested PipelineRun view function as expected.
• The status (e.g., Running, Succeeded, Failed) of the overall workflow accurately reflects the status of its constituent nested pipelines.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated