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.
What | Detail |
|---|---|
Time | About 2 hours. |
You will build | A Makefile and a CI workflow that anyone can run, with versions pinned. |
You are done when |
|
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 | What it covers | Level |
|---|---|---|---|
6.1 | One command for the whole loop, explained piece by piece. | W | |
6.2 | How a script knows a run passed. | W | |
6.3 | Read a thirteen-line workflow line by line. | W | |
6.4 | Four levels of pinning and what each costs. | W | |
6.5 | Fast checks on every change, heavy sweeps overnight. | W |
Lessons are in learning order: each one sets up the problem the next one solves. The glossary and the command cheat sheet are open to you throughout; if something fails, go to the troubleshooting table.