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.
dagger.io/blog/dagger-10-bet…
We're going with @dagger_io because it fits Wind Stream's architecture so well. Dagger's checks are content-addressed, so we can prove that the same change gives the same receipt wherever it runs.
A @dagger_io customer had an issue with pipelines hanging for 1hr pulling a node dependency.
As Dagger Cloud is the only CI that charges by actual usage, they paid nothing for the time the pipline was stuck.
Pick the product which alings incentives
dagger.io/pricing
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.
dagger.io/blog/dagger-for-gi…
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.
entire.com/blog/continuous-i…
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.
dagger.io/blog/dagger-for-en…
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.
dagger.io/blog/dagger-10-bet…
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 👇
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 😁
dagger.io/ 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
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.
Ask your agent about trying Dagger 1.0 😇
One API for orchestrating environment setup, builds, tests, codegen, and the DAG that connects them.
Run the same pipelines before and after push, with shared compute and cache.
Open source, runs locally or in cloud.
love dagger been using it and provisioned dedicated server and migrated to a more pipeline approach.
this also does not include all the extra stuff we can run in the background like dbt and other data pipeline work during off hours or a low priority queue