Building Ruby Head for your Rails App
summary
Claim: run Ruby head on CI so regressions surface before production. Actual work: build Ruby head with ruby-build inside a Dockerfile, push images to Docker Hub, schedule nightly Buildkite builds and run Rails test suites; result: a working pipeline that caught a real deadlock introduced after 3.0.1 and sped Gusto’s upgrade (project spans ~3–4 months, one month after root cause). Tools: Docker, Buildkite, ruby-build, optional jemalloc via LD_PRELOAD or compile flag, and a nightly Docker image pushed workflow.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:19Benefits of Gradual Ruby Upgrades
- 10:49Disadvantages of Gradual Ruby Upgrades
- 17:57Building Ruby Head on Docker
- 31:141. Compilation Flag
- 32:49Compilation flag vs. Preloading library?
related talks
49mRuby Software Continuously Delivered and Exhaustively Explained
54mBuilding and Managing a Ruby Infrastructure
25mRuby in containers
40mDeveloping Ruby Applications with Docker
01h 01mShipping Ruby Apps with Docker
28mKeeping Developers Happy with a Fast CI
40mContainerized Ruby Applications with Docker
32mHow We Distribute Ruby to the World
