Lesson 1: A release that had to be rolled back · 7 min
Before you begin · The Friday release · What went wrong
Learners sign in, so every finish and score is recorded. 7 fields to fill in with your details.



Minutes are an estimate.
Before you begin · The Friday release · What went wrong
Events and owners · Who owns it? · Check
The pipeline · Order the steps · Broken build
Flag or branch? · A risky feature · Clean up
Safe deployment · Rollback drill · Check
A blame-free retrospective · Raise it early · Practice
Taken from the course itself.
What would best have prevented the long night?
Answer: Small, frequent, rehearsed releases. Small releases are easier to understand and to undo, and rehearsal removes surprises.
Lesson 1: A release that had to be rolled back
Why fix a red main branch first?
Answer: Every change after it is built on a broken base. A broken base makes every later result untrustworthy.
Lesson 3: Continuous integration and delivery
What is the main benefit of merging behind a flag?
Answer: Small merges, and the feature can be switched off fast. A flag separates deploying code from releasing a feature.
Lesson 4: Feature flags and safe releases
The main branch is red and three people keep pushing.
Best response: Stop, fix or revert first.
Weaker responses: Push on; Disable the test; Ask for a day.
Comments from trainers
No comments yet. Tell other trainers how the course went.
Your comment
Comments are public. We remove spam and personal details.