The mechanics.
WHAT A PIPELINE IS
A defined sequence of steps run automatically when something changes.
WHAT TRIGGERS IT
A commit A proposed merge A tag A schedule
WHAT THE STEPS USUALLY ARE
Retrieve the code Install dependencies Run checks and tests Build artefacts Deploy, where appropriate
WHERE IT RUNS
A hosted service, or your own machine.
WHAT TO DEFINE IT IN
A file committed alongside your code.
WHY
So the pipeline is versioned and reviewable, like everything else.
WHAT TO KEEP FAST
The checks running on every change.
WHAT TO MOVE ELSEWHERE
Slow tests, run less frequently.
WHAT TO CACHE
Dependencies, so they are not downloaded every run.
WHAT TO FAIL ON
Anything that would break production.
WHAT NOT TO FAIL ON
Warnings nobody acts on.
WHY
A pipeline that fails routinely is ignored.
WHAT TO NOTIFY
The person who made the change, immediately.
