Dagger

Dagger 0.19 is out, with a LOT of improvements: - Better performance (more on the way!) - Run Dagger without Docker - Local container export - First-class support for codegen workflows - Build-an-agent! Run tiny coding agents directly in your workflows, with perfect context 🧵

@marcosnils @dagger_io This looks beautiful!

What if your CI had a lockfile? #a-lockfile-for-your-ci" target="_blank" rel="nofollow noopener">dagger.io/changelog/#a-l…

FYI. This week we're moving Dagger Cloud to Absurd by @mitsuhiko. Will share our experience if anyone's interested. cc @marcosnils @matiaspan26

When the creator of Docker rewrites buildkit, people should pay attention: x.com/solomonstre/st…

Update: we merged it 😅 The next release of Dagger will be buildkit-free.

FYI, Dagger is about to move off Buildkit, to a cleanroom reimplementation. This matters beyond Dagger. Buildkit is load-bearing infrastructure for a huge chunk of CI/CD. It has fundamental limitations that are getting harder to work around, but it's too entrenched and complex to just rip out. We've been chipping away at it for two years, replacing it piece by piece, and it's finally paying off. And we'll make sure the offramp is available to others too... More once it ships. DM me (here or on discord) if you're curious. #project-theseus-removing-buildkit" target="_blank" rel="nofollow noopener">dagger.io/changelog/#pro…

Say what you want about Jenkins... At least it was open-source. There's a new cohort of CI vendors who like to make bold claims... Not bold enough to share their code, though!

If you want faster CI, focus on caching. Dagger remains the only CI platform that caches every operation by default. Zero configuration needed. That's not a feature you can bolt on: you have to design for incremental execution from day one. Then the performance gains compound👇

Introducing cache control for Dagger modules. Dagger executes your CI pipelines incrementally: when a pipeline runs twice, it skips work that’s already done and can complete faster. This caching process happens automatically, sparing you the pain of maintaining fragile configuration files. But until now, only system functions could be cached in this way, and not functions defined in a module... So, as of Dagger 0.19.4, module functions are cached by default. To cache module functions by default, we needed a way to know whether your function is pure. A function called deploy() looks the same as build() to the engine, and caching the wrong one would break your pipeline. The solution is to annotate deploy() to let us know that it has a side effect. That is the purpose of cache control. dagger.io/blog/cache-con…

The best teams are already collapsing this down to 2 jobs: 1. Front office: people who talk to customers and ship. 2. Back office: people who keep systems running. Don't tolerate "hot people" who can't ship, or "slop cannons" who can't talk to users directly.

@davidfowl 👀

CI/CD pipelines are due for a do-over in the agentic era...

Shipped: GCP Secret Manager is now a native Dagger secret provider. `gcp://my-secret` works with ADC, service account keys, and Workload Identity on GKE. No wrapper scripts, no shell glue. That's four cloud secret backends supported natively: AWS, GCP, Vault, 1Password. Which one should we add next? #new-secrets-provider-gcp-secret-manager" target="_blank" rel="nofollow noopener">dagger.io/changelog/#new…

Coming soon: `dagger check --failfast` Designed to shorten your agent's feedback loop: instead of waiting for an entire suite to finish, agents get the first failure immediately and can start fixing it. #fail-fast-mode-for-dagger-check" target="_blank" rel="nofollow noopener">dagger.io/changelog/#fai…

New: Dagger integrates natively with AWS Secrets Manager and Parameter store. #aws-secret-providers" target="_blank" rel="nofollow noopener">dagger.io/changelog#aws-…

So, we made one of those fancy changelogs: dagger.io/changelog

@ajaegle @marcosnils We are building this, layered on top of our engine. In early access for now. Want a demo? 😁

@marcosnils @dagger_io I‘m fully convinced on using dagger for the definition/coding part. What‘s your goto solution to replace the trigger part? Is there a minimal solution to manage the jobs (webhook/polling git, secrets management, overview about runs) that is not tied to github?

What's the future of CI and software delivery according to GEO? @dagger_io

🎥 Replay dispo ! Mon talk à la @CNDFrance est en ligne 🚀 Salle comble 🙏 🐳 @Docker Bake, builds en parallèle + présentation des features ⚙️ Bake dans les outils de CI CD, App Python + CI as Code avec @dagger_io 👉 Lien en commentaire Merci à l’orga et à la communauté ❤️

How did we unlock a fully local, cached, reproducible build and release CI/CD that cross compiles Go CGO binaries? With @dagger_io and @ziglang of course!! johncodes.com/archive/2026/0…

If your development loop in the agentic era feels somehow broken mostly because CI (looking at you GHA), you might want to check @dagger_io to help with that. Dagger gives syou: - local first execution - repeatable builds - programmable API - observability out of the box 👇

Our commitment @dagger_io is to deliver a better way to ship software for both humans and agents. A big part of that is keeping the iteration loop as smooth and fast as possible. We just released 0.19.10 with lots of fixes and perf improvements. Gotta keep 🚢