Skip to content
Testaroo
yaml755 B

Tekton PipelineRun (Run Request)

A Tekton PipelineRun as a run request: a pipelineRef, params, timeouts and a workspace binding, with no status block. A completed run's status is a record of what happened and belongs with test-report fixtures, not with pipeline definitions.

Config testingConfig parsingEditor testing
Preview, first 29 linesyaml
# A PipelineRun is a run REQUEST: a spec that asks for an execution. It carries no `status`
# block, because a completed run's status is a record of what happened and belongs with test and
# CI report fixtures, not with pipeline definitions.
apiVersion: tekton.dev/v1
kind: PipelineRun
metadata:
  generateName: build-and-verify-
  namespace: example-apps
spec:
  pipelineRef:
    name: build-and-verify
  params:
    - name: revision
      value: v1.4.0
  timeouts:
    pipeline: 1h0m0s
    tasks: 45m
  taskRunTemplate:
    serviceAccountName: example-build
  workspaces:
    - name: shared
      volumeClaimTemplate:
        spec:
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 1Gi

Specifications

System
Tekton
Kind
PipelineRun
Has Status Block
false
Timeout Pipeline
1h0m0s
Workspace Binding
volumeClaimTemplate
Boundary
run request, not a run record

Testing contract

Expected to pass
Scenario
Distinguish a Tekton run request from a completed run record
Expected result
The document binds a pipelineRef with params, timeouts and a volumeClaimTemplate workspace, and carries no status block to mistake for a result

What is a .yaml file?

YAML (YAML Ain't Markup Language) is a human-readable data-serialization format using indentation, key-value pairs, and lists, and is a superset of JSON. It supports comments, anchors, and multiple documents per file, favoring readability for configuration. Its indentation sensitivity makes it error-prone to hand-edit.

How to use this file

Use an example YAML file to test config parsers, indentation and anchor handling, multi-document streams, and safe-loading to avoid arbitrary object construction.

How to use this file for testing

“Tekton PipelineRun (Run Request)” is a deterministic Testaroo fixture for Config testing, Config parsing, Editor testing. TOML, INI, YAML, .env, and dotfile configuration samples with nested sections and typed values, for testing config parsers, loaders, and environment tooling.

Documented properties for this file: YAML · 755 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Pipeline and infrastructure fixtures are inert configuration: steps reference fictional images and scripts, and nothing here executes. Run your linter, schema validator, migrator, or policy engine against them, and expect the deprecated-syntax and intentionally invalid variants to be rejected.

Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.

Code examples

import yaml  # pip install pyyaml

with open("tekton-pipelinerun.yaml") as f:
    data = yaml.safe_load(f)
print(data)

Generated by generation/pipelines.py. Free for any use, no attribution required, license.

Related files