Optimizing CI/CD Pipelines for Faster Time to Market
summary
Shows concrete fixes and results: switching Dockerfiles to multi-stage builds reduced image from 657MB to 157MB, creating shared base images speeds builds by ~2 minutes in CI and ~4 minutes locally, and removing a single overly-broad CI trigger cuts concurrent compute from ~120 minutes to <20. Moves from legacy Node monoliths toward Go microservices halves typical response time from ~5s to ~2.5s. Recommends regular repo audits, local prechecks, CI usage limits and GitOps/K3s integration.
AI-written summary · about
chapters (4)
- 0:00Introduction to CI/CD optimization
- 11:23Case studies from real experiences
- 21:17Identifying pipeline bottlenecks
- 26:11Closing and Q&A
related talks
26mOptimizing Your CI Pipelines
41mContinuous Integration Tips & Tricks
22mEmbedded Software Development Efficiency Improvement with Docker and Kubernetes
01h 26mOptimising Continuous Delivery
01h 02mContinuous Integration: Tips & Tricks
32mPractical Tips & Tricks for CI/CD Success
27mThe Need for Speed (in your CI/CD setup)
24mCI/CD Best Practices to Deliver Software Faster