CI/CD Reimagined: Building Portable, Composable Pipelines with Dagger
summary
Dagger replaces YAML pipelines with real code (Go, Python, TypeScript) that generates GraphQL queries and runs on a Docker-backed DAG engine so CI runs identically local or remote, caches pipeline layers, and parallelizes matrix builds. Kubernetes support arrives via a Helm chart, Dagger Cloud gives a free profiler with OpenTelemetry traces, and an ask_llm module can auto‑generate tests or refactor Dockerfiles. The demos show builds, caching, and deploy hooks actually working.
AI-written summary · about
chapters (15)
- 0:00Dagger introduction
- 4:05CI/CD pipeline problems
- 6:16Dagger vs YAML
- 8:27Docker and Dagger impact
- 10:56Pipelines in code
- 13:52DAG engine execution
- 16:37Caching and Kubernetes
- 18:26Matrix builds simplified
- 21:16Debugging with Dagger Cloud
- 27:03Daggerverse modules
- 28:51AI in Dagger
- 33:29Q&A: Deployment
- 35:22Q&A: Upgrade paths
- 37:55Q&A: Security concerns
- 40:22Q&A: Local development
related talks
56mCutting-Edge Continuous Integration with Dagger
26mFuture-Proof Your Platform’s CI/CD Without Developers Noticing a Thing
30mDagger at Scale: How Not to Stab Yourself with Your Pipelines
31mNo More 'git commit -m "fix pipeline #42"' Thanks to Dagger
29mIntroducing Dagger Modules: Open Source CI/CD Building Blocks You Already Know How to Write
27mWrite portable CI/CD pipelines using Python
40mSharpen up your CI/CD pipelines with Dagger
05mNavigating the World of Pipeline as Code: Insights and Strategies with Dagger