What does it look like to build a modern CI/CD pipeline from scratch in 2024? While many of you would pick GitHub Actions and be done with it, how do you run it locally? And what do you need to do to get caching to work?

Tom Chauveau joins us to help Alex Sims build a modern CI/CD pipeline from scratch. We start with a Remix app, write the CI/CD pipeline in TypeScript and get it working locally. While we don't finish, this is a great start (according to Alex).

This was recorded in January 2024, just as Dagger was preparing to launch Functions in the v0.10 release. While many things have improved in Dagger since then, the excitement & the joy of approaching CI/CD with this mindset have remained the same.

LINKS

• 🎬 Modern CI/CD from Scratch (using Dagger TypeScript Modules)
• 🎉 Introducing Dagger Functions (a.k.a. Dagger Modules)
• 🌌 Daggerverse

EPISODE CHAPTERS

• (00:47 ) - Intro
  


• (01:35 ) - Current CI/CD pipeline
  


• (03:40 ) - Why not a single pipeline stage?
  


• (04:29 ) - Dagger expectations
  


• (05:18 ) - Thinking of retiring GitHub Actions
  


• (05:48 ) - Why the GitHub Actions & Jenkins split?
  


• (06:46 ) - TypeScript in Dagger Modules
  


• (08:40 ) - Modules extend the Engine API
  


• (09:45 ) - Plan for today
  


• (10:57 ) - Pairing session conclusions
  


• (12:11 ) - Is it faster?
  


• (13:10 ) - Re-using the cache between runs
  


• (14:50 ) - Key takeaways
  


• (19:04 ) - What comes next?
  


• (22:43 ) - Not if you are using Jenkins
  


• (23:33 ) - Thank you