The Need for Speed (in your CI/CD setup)
summary
Claim: a real all-day build gets reduced to minutes by specific actions not platitudes. Concrete fixes used on CircleCi include increasing resource class to match developer laptops (local 3–5 min vs CI 20+ min), test splitting by time into parallel shards, aggressive caching of dependencies and artifacts, baking tools into custom images and enabling docker layer caching. The monster build from 2015 gets tamed: removing low-value tests and narrowing scope plus these tactics yields fast, reliable pipelines.
AI-written summary · about
chapters (9)
- 0:00Faster CI/CD builds
- 5:21Slow builds frustrate teams
- 9:29Identifying slow builds
- 13:41Boosting build performance
- 15:26Parallelizing jobs and tests
- 17:11Caching dependencies
- 20:41Reducing test scope
- 22:48Team collaboration in CI/CD
- 24:16Defining build time
related talks
46mThe Need for Speed (in Your CI/CD Setup)
46mDeveloper Productivity at Scale
24mCI/CD Best Practices to Deliver Software Faster
32mPractical Tips & Tricks for CI/CD Success
25mContinuous Delivery, high-performing engineering teams, and the Holy Grail
20mMaximize development efficiency with expert CI/CD strategies
27mOptimizing CI/CD Pipelines for Faster Time to Market
48mDemystifying CI/CD