The Need for Speed (in Your CI/CD Setup)
summary
Slides and captions list concrete tactics and measurable outcomes: use CircleCI resource_class to match developer machines, run jobs in parallel and split huge test suites, cache dependencies and artifacts, and enable docker layer caching to avoid reinstalling and rebuilding. A real team suffers an all‑day build and 15‑hour runs then cuts feedback time to minutes by resizing machines, splitting tests, and reusing images. Examples include npm caching, artifact reuse, and per-repo cache keys; each technique states the problem it fixes and how success is measured.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:18The story of an all day build...
- 4:53Build failed
- 13:54When are slow builds a problem?
- 16:39What do you measure?
- 20:14BIGGER, FASTER MACHINES
- 22:42GO PARALLEL
- 25:38CACHING
- 26:10Dependencies -Use the right Docker image for your needs
- 32:49TEAMWORK (MAKES THE DREAM WORK)
- 35:05What is the right build time for your team?
- 36:43CI/CD IS NOT A RACE
- 38:52Practical tips for optimising your CI/CD pipelines (when your tests take all day)
related talks
27mThe Need for Speed (in your CI/CD setup)
32mPractical Tips & Tricks for CI/CD Success
24mCI/CD Best Practices to Deliver Software Faster
48mDemystifying CI/CD
31mCI/CD Agility and Controlling Pipeline Sprawl
26mFaster, Cheaper, Leaner: Horizontally Scaling a CI Pipeline
41mContinuous Integration Tips & Tricks
33mHigh performing engineering teams and the Holy Grail