Accelerating Product Innovation with OSS CI as Code
summary
Shows how Dagger turns CI into code (Go/TypeScript/Python) using Dagger functions and OCI containers so pipelines run the same locally and in CI. Example: a docs-feedback feature is checked out, dagger CLI builds containers, starts services, emits a localhost URL so a PM can validate the UI — no heavyweight setup. Workflows plug into GitHub Actions, Jenkins, GitLab, etc., reuse functions across languages, enable preview environments without heavy infra and cut CI-only debugging.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:28What is continuous integration
- 3:57Why teams adopt CI
- 8:08Debugging CI failures
- 10:14Introducing Dagger
- 12:00Product manager workflow
- 16:35Dagger workflows in practice
- 18:41Adopting Dagger incrementally
- 19:02Summary
related talks
42mCI/CD Reimagined: Building Portable, Composable Pipelines with Dagger
27mRun Your CI in Code, Not YAML
30mDagger at Scale: How Not to Stab Yourself with Your Pipelines
33mThe “C” in CI/CD is not for “Closed”
32mNavigating the Sea of Javascript tool
19mHow to utilize Open Source tools to create CI/CD & DevOps workflows
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
39mCI/CD, APIs, and Scaling: What Every Cloud Native Developer Needs To Kn...