Evolving CI/CD at Flipkart
summary
Flipkart builds an in‑house CI/CD platform called Flow on Argo Workflows, Rollouts and Helm and runs it at scale — 8K+ builds and 1K+ prod deployments per day, 6M pipeline runs total, managing ~3K production services and 2K tenants. Claims include a 50% faster build time via BuildKit + remote layer cache, node‑pool partitioning for short vs long jobs to double throughput without more nodes, shared‑disk worker pools for artifact locality, ephemeral dev deploy environments, canary rollouts with approval and an 80% code‑coverage gate.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:49Demo
- 13:20Flow
- 13:49Goals for Flow
- 14:47Flow Architecture
- 15:41Worker Pool
- 16:07Control Plane
- 16:22Pipeline
- 17:23Challenges
- 19:54Slow Pipelines
- 22:12Overprovisioning
- 22:26Build Problems
- 22:52Deployment Issues
- 23:46Incorrectness
- 24:16QA
related talks
46mThe Software Factory
54mFrom Code to Customer
41mContinuous Delivery Transformation: The New Way of Working
35mPanel: GitOps User Stories
48mDevOps Culture & Practices to Create Flow
43mGitOps at Scale with and Argo CD on
31m20k Leagues Under Platform Engineering
29mWe Have Always Done It This Way! Now Let’s Try Something Completely Different