Manuals / CI/CD Pipelines / Chapter 10

D · Governance · advanced · Week 7–8 · Chapter 10 of 12

Rollback, recovery & incident response

Ship knowing how to un-ship. Revert commits, redeploy previous artifact, feature flags — optimize mean time to recovery (MTTR).

Path progress
77%

Step 1 of 4

Rollback runbook

Step-by-step: detect bad deploy, revert commit or redeploy tag, verify health, communicate.

Rollback runbookDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Rollback runbookdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Write ROLLBACK.md — target <15 min recovery for your lab app.

Was this step clear?
Chapter learning outcomes
  • Revert vs fix forward
  • Deploy previous artifact
  • Runbook format
  • MTTR

Clear these before you leave

Side quest

Timed drill

Time yourself: break staging → recover. Beat 15 min?