Sharpen up your CI/CD pipelines with Dagger
summary
Claim: a PHP SDK launched as a community‑supported way to write Dagger modules that use Docker and the GraphQL API so pipelines run identical locally and in CI. Demonstrations show generated modules with attributed functions, composer and PHPUnit inside containers, live interactive debugging drops to shell, and a dagger develop cycle to refresh definitions. Reusable modules install from GitHub and mix languages, CI config shrinks to simple dagger calls, and the approach is shown working end‑to‑end.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:05CI pipeline challenges
- 6:19Dagger for CI pain points
- 11:40Dagger modules and SDKs
- 12:01Initialize Dagger module
- 18:28Module structure and attributes
- 25:53Reusable objects in modules
- 26:25Basic Dagger pipeline
- 30:21Reusable modules and cross-language
- 34:37Dagger in CI environments
- 37:07Resources and community
- 38:56Q&A
related talks
56mCutting-Edge Continuous Integration with Dagger
29mIntroducing Dagger Modules: Open Source CI/CD Building Blocks You Already Know How to Write
42mCI/CD Reimagined: Building Portable, Composable Pipelines 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
27mWrite portable CI/CD pipelines using Python
31mNo More 'git commit -m "fix pipeline #42"' Thanks to Dagger
42mThe Self-Healing Pipeline: How Dagger + LLMs Are Making Traditional CI/CD Obsolete