Future-Proof Your Platform’s CI/CD Without Developers Noticing a Thing
summary
Claims that using Dagger plus containers and general-purpose languages (Go/TypeScript/Python) yields portable CI/CD workflows that run identically on dev machines and CI so teams avoid the usual 5–30 minute push‑and‑pray cycles. Demonstrates replacing YAML DSLs with reusable Dagger modules for Go, wiring build/test/lint and a security scanner into a single pipeline, running it locally with Docker, and shows the pipeline failing fast when a downgraded base image breaks — proving it works. run CI locally reuse modules
AI-written summary · about
chapters (8)
- 0:00CI/CD struggles
- 3:52Developer vs CI drift
- 7:05YAML flaws in CI workflows
- 10:02Dagger for portable CI
- 12:35Live Dagger demo in Go
- 17:18Reusing pipeline modules
- 20:14Security scans without friction
- 23:33Summary & Q&A
related talks
42mCI/CD Reimagined: Building Portable, Composable Pipelines with Dagger
29mIntroducing Dagger Modules: Open Source CI/CD Building Blocks You Already Know How to Write
27mRun Your CI in Code, Not YAML
40mSharpen up your CI/CD pipelines with Dagger
27mWrite portable CI/CD pipelines using Python
56mCutting-Edge Continuous Integration with Dagger
31mNo More 'git commit -m "fix pipeline #42"' Thanks to Dagger
42mThe Self-Healing Pipeline: How Dagger + LLMs Are Making Traditional CI/CD Obsolete