Massively Continuous Integration: From 3 days to 30 minutes
summary
Claim: continuous integration shrinks release certification from three days to ~30 minutes by rearchitecting tests and infrastructure. Uses Jenkins + EC2 cloud formations to spin ephemeral environments, dynamic Selenium grids (IE + Firefox), and page‑object Selenium 2 suites cut from ~1,800 brittle tests to ~750 fast tests running on 16 threads. Built Jenkins description plugin + pipeline view and an AtTask bug-creation integration, runs ~150 commits/day, consumes ~40,000 machine hours/month at ~$8–10k and delivers fast, visible, accountable feedback.
AI-written summary · about
chapters (19)
- 0:00Massive CI introduction
- 1:08Local CI to massive scale
- 2:53ATask CI challenges
- 4:00Legacy CI slow testing
- 5:43Why transform CI pipeline
- 7:26Big goal for CI
- 8:29CI pipeline explained
- 9:55CI performance scalability
- 13:08Selenium tests rewritten
- 15:37Cloud test environments
- 17:41Jenkins dashboard improvements
- 19:06Automated issue creation
- 20:29Integration challenges learned
- 22:12Team adoption and investment
- 24:18Cloud CI cost management
- 25:20Calculating CI ROI
- 27:04Cloud virtualization future
- 27:46Next steps open source
- 35:08Q&A
related talks
01h 00mAutomation Engineer’s Way to Continuous Integration
41mContinuous Integration Tips & Tricks
30mRevolutionizing Continuous Integration with Selenium
45mHighway to Continuous Integration
32mBuilding Continuous Integration and Feedback
45mContinuous Integration: That’s Not What They Meant
01h 01mA team's transition to Continuous Delivery
01h 02mContinuous Integration: Tips & Tricks