TEP-0056: Pipelines in Pipelines. Fine-grained timeout overrides for child PipelineRuns.

[twoGiants]

Feature request

Add a pipelineRunSpecs field to PipelineRunSpec (alongside the existing taskRunSpecs) to provide fine-grained timeout control for child PipelineRuns. This enables setting timeouts.pipeline, timeouts.tasks and timeouts.finally independently on a per-child basis.

pipelineRunSpecs follows the same pattern as taskRunSpecs:

• taskRunSpecs takes a list of PipelineTaskRunSpec to configure how a Task in a Pipeline is run
• pipelineRunSpecs takes a list of ChildPipelineRunSpec to configure how a child Pipeline in a Pipeline is run

ChildPipelineRunSpec contains a PipelineTaskName identifying which PipelineTask the configuration applies to, and a Timeouts field with the fine-grained timeout settings.

This includes:

• Add pipelineRunSpecs field and ChildPipelineRunSpec type to the API
• Apply the specified timeouts when creating child PipelineRuns
• Update docs/pipelines-in-pipelines.md documentation

See TEP-0056: Runtime specification - provide overrides for PipelineRun.

Use case

A parent PipelineRun needs fine-grained timeout control over a child Pipeline that runs security scans, allocating separate budgets for tasks and finally tasks:

apiVersion: tekton.dev/v1
kind: PipelineRun
metadata:
  name: clone-scan-notify-run
spec:
  pipelineRef:
    name: clone-scan-notify
  pipelineRunSpecs:
    - pipelineTaskName: security-scans
      timeouts:
        pipeline: "0h0m60s"
        tasks: "0h0m40s"
        finally: "0h0m20s"

[beanscg]

Bean Labs took a public-source pass on this issue.

The narrowest useful next step looks like: Offer a concise wording/example clarification for docs/pipelines-in-pipelines.md after verifying the current page.

Public evidence checked:

• Open public issue in tektoncd/pipeline; repo license Apache-2.0; no assignee; 0 comments.
• Labels: kind/feature.
• Referenced files/paths: docs/pipelines-in-pipelines.md, 0056-pipelines-in-pipelines.md.

A good acceptance check would be a narrow public change that directly exercises the issue's reported boundary.

No PR opened from this pass.