Docs · Glidepath

Pipeline examples

Ten complete, schema-valid cicd.yaml files, each fully commented, covering the shapes you’re most likely to actually want. Copy whichever is closest to your needs and adjust.

Every file here is validated against schemas/cicd.schema.json and rendered through the real Helm chart as part of this repo’s own checks - if it’s in this folder, it works.

#	File	Shape
1	01-minimal-build-only.yaml	`build` only - the smallest valid config
2	02-standard-ci.yaml	`build` → `test` → `deploy(dev)` - the common case
3	03-pr-validation.yaml	PR builds, separate from the main push flow
4	04-multi-env-promotion.yaml	dev → staging → governed `release`
5	05-release-on-tag.yaml	Git-rooted release, triggered by a version tag
6	06-release-branch-fast-track.yaml	A `release/*` branch skips dev entirely
7	07-multiple-tests.yaml	Two TestWorkflows against one build
8	08-containerfile-only-build.yaml	Whole build inside a multi-stage Containerfile
9	09-ephemeral-environments.yaml	A live preview environment per PR/branch
10	10-production-grade.yaml	Everything together - path filters, caching, governance, notifications

Quick visual index

flowchart LR
    subgraph ex1["01 - minimal"]
        direction LR
        a1[build]
    end
    subgraph ex2["02 - standard CI"]
        direction LR
        a2[build] --> b2[test] --> c2[deploy dev]
    end
    subgraph ex4["04 - multi-env promotion"]
        direction LR
        a4[build] --> b4[test] --> c4[deploy dev] --> d4[deploy staging] --> e4[release]
    end
    subgraph ex5["05 - release on tag"]
        direction LR
        a5[release]
    end
    subgraph ex6["06 - release-branch fast track"]
        direction LR
        a6[build] --> b6[deploy staging] --> c6[release]
    end
    subgraph ex7["07 - two TestWorkflows"]
        direction LR
        a7[build] --> b7["test: smoke"] --> c7["test: integration"] --> d7["deploy dev"]
    end

    style ex1 fill:#e8f4fd,stroke:#4a90d9
    style ex2 fill:#e8f4fd,stroke:#4a90d9
    style ex4 fill:#fef3e2,stroke:#d9954a
    style ex5 fill:#fef3e2,stroke:#d9954a
    style ex6 fill:#fef3e2,stroke:#d9954a
    style ex7 fill:#e9f7ef,stroke:#4ab97e

(03, 08, 09, 10 aren’t shown above since they’re variations of build strategy / platform features rather than a different flow shape - see the table.)

Picking one

Just getting started? → 01, then 02.
Want PRs validated before merge, without deploying them? → 03.
Need a real promotion path with human review before production? → 04.
Cut release branches/tags deliberately rather than auto-promoting every commit? → 05 or 06.
Have more than one kind of test to run? → 07.
Build entirely inside Docker, no separate build script? → 08.
Want reviewers to see a live version of a PR before merging? → 09.
Want to see a realistic “everything a real service needs” config? → 10.

See ../quickstart.md for how to go from any of these to a running pipeline, and ../cicd-yaml-reference.md for what every field means.