Migrating CI/CD from Jenkins to Argo
summary
Intuit runs Jenkins on Kubernetes for ~6,000 developers and ~100,000 jobs/day across ~150 nodes, ~200 controllers and up to ~1,500 agents, and migrates CI/CD to Argo Workflows + Argo CD to cut cost and complexity. Migration shows one pod per step for autoscaling, DAG parallelism by dependency, workflow templates for reusable logic, PVC-based artifact passing, Prometheus pipeline metrics, and a staged migration path (trigger Argo from Jenkins first) with working examples and a Pipekit control plane.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03Jenkins at scale challenges
- 3:14Jenkins inefficiencies
- 5:44Pip kit challenges with Jenkins
- 7:54Why Argo workflows
- 10:01Jenkins vs Argo
- 11:48Jenkins to Argo mapping
- 13:11Jenkins vs Argo pipelines
- 17:10Jenkins vs Argo comparison
- 21:44Migration strategy to Argo
- 23:50Migration resources
related talks
12mLightning Talk: Migrating 1,300 Jenkins Jobs To Argo Workflows: Lessons From a…
27mLeveraging Argo Workflows To Move, Migrate and Manage All of Your Workflows
18mNavigating the Shift to GitOps: Overcoming Challenges in Migrating from Jenkins..
12m⚡ Lightning Talk: On-Premise and SaaS CI/CD Large-Scale Production Automation with Argo Services
29mLarge Scale Batch Processing with Argo Work...
46mFrom FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp
43mGitOps at Scale with and Argo CD on
27mArgoCD as the Engine of a Brownfield Migration to Kubernetes