Linters, migrators, and policy engines that read pipeline definitions need real ones to read. This category ships workflow and build definitions across the systems teams actually run: GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, Tekton and Argo manifests, Jenkinsfiles, Makefiles, and Gradle builds. Infrastructure-as-code covers Terraform configuration and variable files, generic HCL, and Kubernetes manifests. Data-orchestration fixtures carry Airflow-style DAGs, CWL workflow descriptions, and DAG graphs in Graphviz and Mermaid so a visualiser can be tested against a documented topology. Valid, deprecated-syntax, and intentionally invalid variants are labelled in title and description, and every fixture is inert configuration, no scripts that do anything if run.
Filter pipelines on Browse · 115 files · 16 subcategories
Results start with a representative from each related test family. Use a card’s variant menu or the filters below to reach a specific format, profile, or failure case; every sample retains its own detail page and download.
GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, Tekton and Argo manifests, Jenkinsfiles, Makefiles, and Gradle builds, plus Terraform, HCL, and Kubernetes manifests for infrastructure-as-code.
They are inert configuration fixtures for linters, migrators, and policy engines. Steps reference fictional images and scripts, and nothing here is an executable.
Yes, deprecated-syntax and intentionally invalid workflow fixtures are labelled in both title and description so schema validators can be tested on the failing case.
Start with one example from each use-case group, then continue through its other test families. Choose a use case, search, or filter to find a specific profile; a card’s variant menu contains its related samples.
110 test families · 115 available files · Page 1 of 7
Airflow
An Airflow DAG definition in the classic operator style, using only the no-op EmptyOperator so the file describes a topology and performs no work. Carries the six-task ETL graph shared across the Airflow JSON, Argo, Grap
Argo Tekton
An Argo CD Application with automated sync, prune and self-heal, retry backoff, sync options, and an ignoreDifferences rule that exempts replica counts from drift detection. All Git and cluster endpoints are example.inva
Azure Pipelines
Azure's named-leg matrix form, where each leg is a mapping of variables rather than an axis product: three Python legs, a maxParallel cap, a job timeout, and a JUnit results publish step that runs on failure too.
Build
A Gradle Groovy DSL build script with a plugins block, a Java toolchain, five dependency configurations, task configuration via named() and a registered task. Every coordinate and repository is fictional, so nothing reso
Circleci
A CircleCI 2.1 config with a two-job workflow, a fallback cache-key list, workspace persistence between jobs, and a test-results store. The baseline the other CircleCI fixtures vary from.
Cwl
A CWL v1.2 CommandLineTool with typed inputs, positional and prefixed bindings, a JavaScript outputEval expression, resource requirements, a Docker hint, and an IANA $namespaces block. Inert: it describes an invocation a
Dag Graphs
The shared six-task ETL topology as a Graphviz digraph, with node and edge defaults, per-node attribute overrides, a same-rank constraint and C-style comments. Carries the identical graph to the Airflow, Argo, CWL and Me
Docker
Compose with three x- extension fields carrying YAML anchors that are merged into services. The trap is ordering: a tool that strips x- keys before parsing the YAML destroys the anchors and the file stops resolving.
Github Actions
An action.yml-shaped composite action definition with typed inputs, a declared output bound to a step output, and a branding block. Distinct from a workflow file, and a common blind spot in workflow linters that only und
Gitlab Ci
GitLab's `!reference` custom YAML tag used three ways: inside a script list, as a whole after_script value, and as a whole rules value. A stock YAML 1.2 loader has no constructor for it and raises; GitLab's loader resolv
Hcl
An intentionally invalid HCL2 document: an unclosed block, a colon assignment, a half-quoted block label, and a heredoc whose terminator is misspelled so it swallows the remainder of the file. Four documented faults, eac
Helm
A Helm v2 Chart.yaml with two conditional subchart dependencies, semver range constraints, a kubeVersion constraint, maintainers and annotations. Every repository and URL is example.invalid, so nothing resolves anywhere
Jenkins
A declarative Jenkins matrix over two axes with a nested excludes block: six platform/arch combinations minus the windows arm64 pair leaves five cells, documented in the specs so an expansion can be scored exactly.
Kubernetes
A CronJob with an explicit timeZone, Forbid concurrency, a starting deadline, and history limits on both success and failure. For testing cron parsing and the scheduling fields policy engines most often check.
Terraform
An intentionally invalid Terraform configuration: an unclosed resource block, a colon where HCL needs an equals sign, a reference to an undeclared resource, and a resource block missing its second label. Four documented
YAML Edge Cases
Anchors and aliases across mapping, sequence and scalar nodes, including an anchor nested inside another anchored node. The point most tooling misses: an alias is a reference to the same node, so a shallow-loading parser
Airflow
A decorator-based Airflow TaskFlow DAG where dependencies are implied by function calls rather than >> operators: the shape static DAG extractors most often get wrong. Every task returns a literal, so nothing performs I/
Argo Tekton
An Argo CronWorkflow wrapping an inline workflowSpec: a cron schedule with an explicit timezone, Replace concurrency, history limits, and a suspend flag. Nested-spec shape that flat schedule extractors miss.
The use-case group filter replaces the long list of category sections.
