Announcing Dagger 1.0 beta.
Replace Jenkins and GitHub Actions with CI that matches the speed and scale of coding agents without wasting compute or tokens.
Featuring: test-native CI, dev shells, local and remote execution, official modules, and more.
https://t.co/HgVwTUAJi3
Announcing Dagger for GitLab.
Run the same checks before and after push. See results in your terminal and merge request.
Cut out the middleman: just GitLab and Dagger Cloud.
Stop wasting compute: checks are cached, and you pay for exact usage, not machines.
https://t.co/hh1CDlTmP5
@mauricioTechDev@GoEntire The engine and CLI are open source, you can run them locally or self-hosted, for free 😁
Dagger Cloud is optional. It provides managed engines, with scale-out, distributed cache, observability, and access control. No free tier, but we have a free trial!
https://t.co/WvBuh1OrWT
As agents transform software development, it’s not just your forge that has to be reinvented, it’s your CI solution, too.
Today, we’re rolling out a new partnership with @dagger_io, so you can natively run your CI on Entire, right next to your code and context.
https://t.co/gCXuUUVAAp
Announcing Dagger for Entire.
Goodbye pull requests! @GoEntire is a new Git forge for agents and humans. Now with native Dagger support.
Agents run the same checks before and after push, with a shared cache and without melting your machine.
https://t.co/xbnbh3y6ze
1.0 is a reinvention of Dagger driven by one thing: pain.
Specifically the pain experienced by our earliest adopters since 2022. We have great success stories, but we also lost users along the way.
Here's what we learned 👇
https://t.co/z620e8b8oN Really is the ‘portal 2’ of CI. Knowing where you are already ‘trying to land’ through the DAG and how impactful high velocity CI infra is when it starts in local dev feels great. The paradigm shift is real
Dagger 0.1 launched in 2022 and it was VERY different...
- Just the engine, not a complete CI platform. No scale-out, no distributed cache, no forge integrations, you had to DIY.
- We emphasized the ability for devs to write their own CI in their favorite language - turns out devs don't want to deal with CI no matter the language.
- too slow to be useful in the devloop
- most of all: CI was just not a priority. Platform team loved it and "snuck it in", but strong inertia from management and dev. When the champion left, adoption would stall.
Still plenty of successful pre-1.0 users: Fastly, Fidelity, Nvidia, Playstation, Nine media, and many others. But they had to put in the work.
For 1.0 we spent a year filling all these gaps, and coding agents took care of the inertia 😁
I hate it when CI providers insist on reinventing secret stores. We already have @1Password, @hashicorpvault, @infisical, AWS, GCP, Azure. Not to mention OIDC. Why one more silo?
@dagger_io integrates with all of these. Your secrets become nodes in the DAG, fetched on demand.
Zoom out. CI is the whole DAG.
Dev sandboxes, builds, tests, codegen, deploys: they're all interconnected, but have no common execution or data model. Why?
Agents need the whole DAG to be fast. But you can't optimize what you can't see.
@dshaw Step 1: can it run in the devloop
Step 2: does it cache everything by default
Step 3: is it open source so your agent can customize it
Step 4: how much compute and tokens does it waste per run
😇
@lassitergregg@dodeja@useblacksmith@boatdotdev Thanks Lassiter! Do you rely on your machine's persistent disk for caching?
Have you tried Dagger Cloud? If so, would love to get your feedback.
Also you should join our discord 😊 https://t.co/WvBuh1OrWT