Highway to Continuous Integration
summary
Uses Jenkins plus OpenStack and Chef to deploy isolated environments, runs PHPUnit tests in parallel with Paratest, and ties build results into JIRA. Starts with ~12,000 tests that take hours on a 16‑core machine, splits and isolates tests, drops to ~1,500 priority tests and cuts integration time from ~6 hours to ~5 minutes (full handler redeploy ~3 minutes). Runs full regression twice daily and uses VM snapshots to restore clean states so master stabilizes in half a day instead of five.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 2:02Classic dev problems
- 3:51What is CI
- 4:12Integration build goals
- 5:59Test time optimization
- 7:03Parallel test execution
- 8:27Tests vs speed trade-off
- 9:52Env deployment optimization
- 10:57Jira integration
- 12:41Integration build process
- 13:48Regression build purpose
- 15:38DB migration problems
- 17:30DB migration solution
- 18:36Fresh build benefits
- 21:10CI implementation results
- 22:57Key takeaways
- 23:22Q&A
- 26:33Tooling and support
- 29:42Writing tests
- 31:47Test/data questions
- 35:00Test optimization experience
- 37:53Dependency handling
- 41:06Continuous Delivery team
- 42:13Database work
- 43:22Team size and structure
related talks
35mMassively Continuous Integration: From 3 days to 30 minutes
40mThe Butler Did It: Putting Jenkins To Work For You
01h 12mPitfalls of Continuous Deployment
41mContinuous Integration Tips & Tricks
01h 00mContinuously delivering PHP projects
44mFrom Zero to Federated at the Speed of Jenkins
30mImplementing Continuous Deployment with Jenkins & Gerritt
01h 00mAutomation Engineer’s Way to Continuous Integration