Ruby Software Continuously Delivered and Exhaustively Explained
summary
Maintains CI servers (CruiseControl.rb, Goldberg) and points to ThoughtWorks Go, Capistrano, Chef/Puppet and Plator, advocating an automated build pipeline that produces a deployable artifact on CI matching prod OS/Ruby, runs unit/integration/functional stages in parallel, and requires one human click to go live. Recommends removing GCC/RVM from production, packaging releases (tar/gem), using feature toggles or branch‑by‑abstraction to decouple deploy from release, and prefers trunk‑based commits with fast CI and peer review.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 2:42Release process evolution
- 7:15Testing for confidence
- 13:29The build pipeline
- 21:25Deployment strategies
- 29:30Feature management
- 44:22Closing and Q&A
related talks
42mCONTINUOUS DELIVERY FOR RUBYISTS
54mBuilding and Managing a Ruby Infrastructure
34mStrong Practices for Rails Applications Continuous Delivery
35mCI/CD and devops with Ruby and Rails
34mGuide to Continuous Deployment with Rails
36mContinuous Deployment with Rails
32mHow We Distribute Ruby to the World
31mRuby Releases Ruby