RSpec: GitHub to Jenkins to Spot Instance Parallelization and Back Again
summary
Pipeline wires GitHub pull requests through the ghprb plugin into a build-flow/workflow Groovy pipeline that shards RSpec files across a 25-wide fleet of ephemeral slaves launched via the ec2 plugin as AWS spot instances. Parallel runners run isolated databases, copy artifacts back, and retry failures; the system cuts test turnaround dramatically — reduced from 90 to 7 minutes — while keeping costs low and tolerating occasional spot interruptions.
AI-written summary · about
chapters (23)
- 0:00Intro
- 2:35Unit Tests
- 3:01Continuous Unit Tests
- 3:13Parallel Tests
- 3:34cruft
- 4:09paralyze
- 4:44GitHub to Jenkins
- 5:17Move Jenkins
- 5:30Build Flow Plugin
- 6:39SpecRunner Plugin
- 7:37Parallelization
- 7:56AWS
- 8:25Spot Instances
- 13:14Build Executors
- 14:16Build Flow
- 14:37Groovy Bug
- 15:41Test Run
- 16:09Placement Server Events
- 16:30GitHub Pull Request Builder
- 16:46Lessons Learned
- 19:47Things That Made This Work
- 20:17ScriptLer
- 21:28Conclusion
related talks
23mRSpec: GitHub to Jenkins to Spot Instance Parallelization and Back Again
44mExtending GitHub Flow with Practical Testing
34mChef and InSpec Builds with Jenkins
39mRemove your Testing Bottleneck with CI/CD Pipelines
43mInfinite Space for Your Tests
23mDistributed performance testing at the push of a button
20mHow to Setup Test Infrastructure
38mDistributed Scrum Development with Jenkins, Vagrant, Fabric and Selenium