Upgrading Rails at Scale
summary
Claims a repeatable Rails upgrade process that cut a yearlong slog to a few months by shipping concrete tools and practices: a Bundler dual-snapshot for rails_next testing, a Minitest reporter that marks failing tests instead of skipping them so CI only fails on new regressions, a deprecation toolkit gem to record and gate new warnings, and percentage-based production rollouts plus profiling. Numbers cited: ~80,000 tests, thousands of failures fixed, rollout from 1–5% upward, and the upgrade succeeds in production.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:54Lessons learnt: Stop the bleeding first
- 12:31Minitest Reporter
- 18:03Componentization
- 20:27Enable deprecation logging in Production
- 27:26Small but quick upgrades
- 28:42Usable for any gem upgrade
related talks
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
28mUpgrading Rails: The Non-Technical Parts
32mZero downtime Rails upgrades
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
36mRuby & Rails Versioning at Scale
36mRuby & Rails Versioning at Scale
25mUpgrading Rails: Everyone can do it and here’s how
33mUpgrading a big application to Rails 5