What breaks: four promotion failures

A TEST ENDPOINT LEFT IN A PRODUCTION APPLICATION, A PUBLISH OVER SOMEBODY MID-TASK, A CHANGE NOBODY COULD ATTRIBUTE, and TWO DEVELOPERS OVERWRITING EACH OTHER. THE TEST ENDPOINT IN PRODUCTION IS THE ONE WITH THE WORST CONSEQUENCES AND THE MILDEST SYMPTOMS. A connection promoted unchanged, and a production application reading — and writing — a test system. Lessons 5 to 7, and it frequently runs for weeks because the pages all work; what is wrong is where the data went, and nothing on screen says so. AND THE REALISTIC VERSION IS PARTIAL, WHICH IS WHY IT LASTS. The main connection was fixed and one page was missed — Lesson 6's hunt — so the application is right almost everywhere and wrong in the place nobody exercised during the checks. THE PUBLISH OVER SOMEBODY MID-TASK IS THE SMALLEST AND THE MOST FREQUENT. Lost work, an odd error, a flow that stopped making…

In this module: Module 14 · Source control, environments and publishing

1. 1What a publish actually doesFree preview
2. 2Versions, and living with two
3. 3Source control, and why a visual tool still needs it
4. 4Branching and more than one developer
5. 5Environments, and what differs between them
6. 6Making endpoints configurable
7. 7The promotion checklist
8. 8Rolling back
9. 9Automating it
10. 10What breaks: four promotion failures
11. 11Lab briefing · Promote and prove it is isolated