Any CIYour own repositoryIntermediate~4h

CI/CD

A pipeline is a claim about somewhere else

Read a real workflow as a graph and say what it costs. Follow the bytes that reach production. Decide whether a cache key hits, and price the hit that should have been a miss. Then diagnose the runs where here and there disagree, and find the way back that is still available.

Start this project See the modules

Modules: 6
Drills: 7
Build steps: 0
Time: ~4h

Walk out able to

Read any pipeline and say what it costs, what it ships, what it quietly assumes about the machine it runs on, and how you would get back.

What you work on

Stages, waves and time

The critical path, and what a gate actually reads.

Artifacts and caches

Which bytes ship, which key hits, what a stale hit costs.

Environments and secrets

Why it passed here, and what a masked value still leaks.

Getting back

The rollback lever a migration left you — or took away.

The pitch

What you practise, and what you leave with

Not something you ship — a written reading of a pipeline you actually have: its cost, its bytes, its assumptions, and its way back.

You will practise

Waves, critical path, and the exit status
Cache keys: hit, restore, miss and the bill
Passed here, failed there — name what differs
Masked secrets, and the lever a migration left

Afterwards you can

Time a pipeline from its job graph
Say which bytes reach production
Decide whether a cache key hits
Choose a rollback lever that still exists

Modules

6 modules, 26 items

Lessons explain one idea. Drills repeat it until it sticks. Build steps make something that exists afterwards.

1
Read the pipeline
~40 min
Say what a workflow runs, in what order, on what — and how long the run takes.
- LessonRead a pipeline you did not write7 min
- LessonStart from a machine with nothing6 min
- LessonRead the verdict, not the log5 min
- DrillWrite the line a workflow needs10 min
- DrillTime a pipeline from its graph12 min
2
Build once, then move it
~24 min
Say which bytes reach production, and what their digest and commit id prove.
- LessonFind the second artifact6 min
- LessonMove one object, change only config6 min
- DrillFollow the bytes to production12 min
3
Cache keys and stale hits
~30 min
Decide whether a key hits, and price the hit that should have been a miss.
- LessonRead a cache key as a claim5 min
- LessonFollow the lookup, in order6 min
- LessonWhen a hit is worse than a miss6 min
- DrillDecide what the cache gives you13 min
4
Here versus there
~39 min
Diagnose a run that passed here and failed there, and remove the difference.
- LessonExplain a test that only fails in CI6 min
- LessonFind the difference by taking it away8 min
- LessonDecide when configuration is read7 min
- LessonA new environment starts empty5 min
- DrillName what differs between two machines13 min
5
What a masked value leaks
~29 min
Say what redaction matches, and name the routes a secret takes out of a run anyway.
- LessonRead a clean log that leaked5 min
- LessonThree ways a value walks past6 min
- LessonSay who can read the secret6 min
- DrillSay what escapes the mask12 min
6
Getting back
~50 min
Pick the rollback lever a constraint leaves you, then read a real pipeline.
- LessonFind the lever you still have5 min
- LessonKnow what each lever cannot undo6 min
- LessonSpot the step that spends a lever6 min
- DrillChoose the lever the constraint allows13 min
- LessonRead a real pipeline end to end20 min