Pipeline Architecture
Stages, fan-out, caching, and the difference between a pipeline and a long script.
5 to work through
-
beginner Multiple choice
A team's pipeline builds the artifact separately for each environment because "the config differs". What is wrong, and what do you propose?
2 min answer -
intermediate
A monorepo's pipeline takes 55 minutes because every commit builds and tests everything. Developers batch changes to avoid it. How do you fix it?
2 min answer -
intermediate
A team's pipeline takes 80 minutes from commit to a deployable artifact and engineers have stopped watching it. How do you approach fixing it?
2 min answer -
advanced
A deployment platform's build queue is forty minutes deep after a popular framework release. Before adding capacity, what should be examined in the queue itself?
2 min answer -
advanced
How should a delivery pipeline be structured for a large monorepo where most changes affect a small part of the system?
2 min answer
3 terms in this topic
Change-Aware Test Selection
Running only the tests a change could affect, determined from a dependency graph - with periodic full runs to verify the selection itself.
patternDeployment Pipeline
The automated path a commit travels from source to production, where every stage is a chance to reject the change and no stage can be skipped.
patternPipeline Fan-Out
Splitting independent verification work to run in parallel, bounded by what genuinely has no ordering dependency on anything else.
Neighbouring topics
Delivery & Release Engineering
General material on getting a change from commit to production safely and often.
Build Reproducibility
Pinned inputs and hermetic builds, so one commit cannot produce two different artifacts.
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
Environment Strategy
How many environments earn their cost, what each proves, and what none of them prove.
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Continuous Integration Discipline
Integrating to the mainline daily, and the test speed and review culture that requires.
Deployment Strategies
Rolling, blue-green, canary and shadow, and the traffic and state each one assumes.
Progressive Delivery
Separating deploy from release, and exposing a change to users in controlled increments.
Rollback & Forward Fix
When reversing is genuinely possible, and designing so that it usually is.
Database Migration Under CD
Expand-contract, backwards-compatible schema change, and migrations that cannot roll back.
GitOps
Declared desired state in version control, with a reconciler closing the gap continuously.
IaC Modules & Drift
Reusable infrastructure modules, state ownership, and detecting what changed out of band.
Policy as Code
Encoding standards as automated admission and plan-time checks instead of review comments.
Pipeline Secrets
Short-lived credentials, workload identity, and why the CI system is a prime target.
Supply-Chain Provenance
SBOMs, signed artifacts, attestation, and knowing what actually went into a build.
Deployment Gates
Automated verification between stages, and the difference between a gate and a delay.
Flow Metrics
Work in progress, flow time and flow efficiency — where a change waits rather than moves.
Change Management vs CD
Reconciling CAB-era controls with continuous delivery without pretending either away.
Multi-Region Rollout
Ordering regions, bake time, and stopping a bad change before it becomes global.