Ignites- The Five Dirty Words of CI
summary
Claim: post‑mortems framed as linear CI tools fail — root cause analysis often yields eight “root causes” and is misleading. Replace five whys with systemic models like Swiss cheese. Say human error is an effect not an explanation. Stop making counterfactual statements and calling external playbooks “best practice” without domain fit. Concrete CI anti‑patterns named: broken builds, flaky tests (“flappers”), “Bob’s Mac” local workflows, merge windows, and storing artifacts as Jenkins build numbers. S3 incident used as an illustrative example.
AI-written summary · about
chapters (4)
related talks
10mTester’s Inferno: 5 Circles of Software Hell
08m“The Forensics of Testing”
50mWhy Everything Is Spoiled
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
45mSmoke Tests and Mirrors - The Magic in Test Automation
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
30mThe Feedback Loop from Hell
43mOne Strategy, One Community: A deep dive into a Global Testing Transformation