Pipeline Patterns
Guides for structuring pipelines as they grow past a single job: gating deploys on approval, running jobs on a schedule, passing configuration between pipelines, and keeping configs maintainable over time.
-
Common Pipeline Practices
Conventions worth adopting early, before a pipeline grows past a handful of jobs.
-
Managing Pipeline Configurations
Strategies for keeping pipeline YAML maintainable as it grows — templating, includes, and file organization.
-
Task Input and Output Scenarios
Worked scenarios beyond the basics: optional inputs, multiple outputs, and passing artifacts across jobs.
-
Gated Pipeline Patterns
Hold a job until a condition is met — a passed version, a manual check, or an external signal.
-
Manual Approval Step
Require a human to approve a job before it proceeds.
-
Time-Triggered Pipelines
Run a job on a schedule using the
timeresource. -
Serial Job Example
Prevent overlapping runs of the same job with
serial: true. -
Pipeline
((vars))Example
Parameterize a pipeline so the same config can deploy to multiple environments.
-
Manually Triggered Job Example
Disable automatic triggering so a job only runs when someone explicitly asks for it.