CONTINUOUS DELIVERY FOR RUBYISTS
summary
Continuous delivery is presented as making deployments routine by keeping every commit deployable and promoting the same artifact through a five‑stage pipeline: build, test, package, deploy, smoke check. Recommended tools include Terraform and Packer for immutable images, Docker plus a Docker registry or gemstash/Nexus for artifacts, and CI with Jenkins using parallel_tests or knapsack and DatabaseRewinder to speed RSpec. Claims: fast deterministic tests (<1 hour on CI), small releases cut mean time to recovery, and automation reduces release stress.
AI-written summary · about
chapters (13)
- 0:00Introduction and survey
- 1:09Origins and rationale of CD
- 5:06Definition and goals of CD
- 6:15Key principles of CD
- 13:53Cultural shift and adoption
- 14:20Example pipeline overview
- 15:49Testing tips and optimizations
- 22:57Handling flaky tests
- 26:55Building and packaging artifacts
- 31:16Deploying with ease
- 34:08Acceptance and smoke tests
- 36:00Benefits and stress reduction
- 39:15Q&A on microservices and CD
related talks
49mRuby Software Continuously Delivered and Exhaustively Explained
34mStrong Practices for Rails Applications Continuous Delivery
30mModern Continuous Delivery
41mAll Things Continuous
38mContinuous Delivery, or the magic button for on‑demand releases
55mThe Rationale for Continuous Delivery
36mContinuous Deployment with Rails
01h 03mYet Another Continuous Delivery Talk