Part 6 answers: How do I make the whole loop rerunnable by anyone, anywhere?
A flow that only works on one laptop from remembered commands is not engineering. This part captures the loop in a Makefile with pass markers and exit codes, records tool versions and shows which of them can be pinned, and adds a CI smoke test that checks every change.
It also draws the line between the smoke test that runs on every push and the nightly regression that can afford to take longer.
Write a Makefile that rebuilds everything and reports pass or fail by exit code.
Record tool versions and say which of them can and cannot be pinned.
Explain what belongs in a smoke test versus a nightly regression.
# | Lesson | Level | Status |
|---|---|---|---|
6.1 | W · Working | ready | |
6.2 | W · Working | ready | |
6.3 | W · Working | ready | |
6.4 | W · Working | ready | |
6.5 | W · Working | ready |
Every lesson in this part is ready. Work through them in order: each one sets up the problem the next one solves.