No More 'git commit -m "fix pipeline #42"' Thanks to Dagger
summary
Dagger is presented as a tool to eliminate repetitive "fix pipeline" commits by running the exact same containerized pipeline steps locally and in CI using BuildKit to build a cached DAG of tasks. The demo shows using Dagger's GraphQL API and Go SDK (with mage) to fetch source, run tests, compile and run a binary (fixing a 2+2 bug), start services like Redis on demand, persist secrets and cache across runs, and perform parallel cross‑compiles for amd64 and arm64, with pipelines expressed as code instead of YAML.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:23CI modern burdens
- 3:12Dagger and BuildKit
- 6:03Demo with Playground
- 10:19Go SDK for Dagger
- 18:48Multi-arch builds
- 21:17Third-party services and secrets
- 25:34Telemetry and graphs
- 25:56Q&A
related talks
42mCI/CD Reimagined: Building Portable, Composable Pipelines with Dagger
56mCutting-Edge Continuous Integration with Dagger
30mDagger at Scale: How Not to Stab Yourself with Your Pipelines
26mFuture-Proof Your Platform’s CI/CD Without Developers Noticing a Thing
27mWrite portable CI/CD pipelines using Python
40mSharpen up your CI/CD pipelines with Dagger
42mThe Self-Healing Pipeline: How Dagger + LLMs Are Making Traditional CI/CD Obsolete
29mIntroducing Dagger Modules: Open Source CI/CD Building Blocks You Already Know How to Write