Release Early and Release Often: Reducing deployment friction
summary
Engine Yard runs the AppCloud repo through an automated pipeline that enforces green builds before merge and deploys merged master to staging and production with one command. The team builds an internal CI called Ensemble backed by a job runner Mason and a chat-controlled bot iBot. Test suite sharding cuts CI to ~12–20 minutes, and the org averages 44 deploys in a month, roughly 20 per weekday and about 1–2 production deploys daily, enabling near continuous deployment with zero downtime for most migrations.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:21Reducing deployment friction
- 2:23Starting a ticket
- 4:33Commits
- 6:11Test Drive
- 9:07Bots Channel
- 11:44Notifications
- 13:00Continuous Integration
- 14:27CI System
- 15:13Merging
- 15:47Edge
- 17:10Deploys
- 17:22Production
- 17:48Automation
- 18:01Forcible
- 18:37Version field
- 18:49Continuous deployment
- 19:48Race condition
- 20:34Notification
- 20:50New Relic
- 21:02Emails
- 21:42Mason
- 22:22Deployment process
- 22:43Unicorn
- 23:39Bundler
- 24:12Migrations
- 24:47Add a column
- 25:08Deploy again
- 25:21Run migrations
- 25:47More examples
- 27:59Work in progress
- 29:51About Engine Yard
related talks
24mContinuous Deployment at Scale
46mContinuous Deployment Workflows
36mContinuous Deployment with Rails
32mContinuous deployment at scale
25mFrom Git Push to Exit
01h 01mA team's transition to Continuous Delivery
47mContinuous Delivery Warstories
30mKeith and Mario's Guide to Continuous Deployment with Rails
