Third-generation CI, built to match the speed and scale of coding agents and give them the guardrails and context they need
Joined February 2021
- Tweets1.8K
- Following208
- Followers8.7K
- Likes1.4K
Pinned Tweet
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…
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…
Dagger retweeted
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…
Dagger retweeted
Dagger is the goat. Using it w all my agents and software factories!!
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…
Dagger retweeted
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 retweeted
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
Dagger retweeted
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.
Dagger retweeted
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.
Dagger retweeted
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
Dagger retweeted
Solid guide. Dagger's modules cleanly handle the usual Playwright+Compose pain points: matching browser images to your lockfile, wiring services so tests hit "frontend" instead of localhost traps, and keeping state ephemeral. Same check runs locally or in Cloud Checks with zero YAML. Per-env project isolation is a practical touch.
How to run playwright tests against docker compose in CI?
dagger.io/learn/playwright-t…
Dagger retweeted
the shared cache is the sleeper feature here.
let the agent run checks on the cloud engine while it works: dagger --engine=cloud. whatever passed before push comes back as a cache hit when the pr opens.
Dagger retweeted
Couldn't recommend Dagger enough if you're looking to improve your CI for the age of agents!
Announcing Dagger for GitHub.
Run the same checks before and after push. See results in your terminal and PR.
Cut out the middleman: just GitHub and Dagger Cloud.
Stop wasting compute: checks are cached, and you pay for exact usage, not machines.
dagger.io/blog/dagger-for-gi…
Dagger retweeted
If your AI moves fast but your CI gets stuck in the middle, whats the point?
Announcing Dagger for GitHub.
Run the same checks before and after push. See results in your terminal and PR.
Cut out the middleman: just GitHub and Dagger Cloud.
Stop wasting compute: checks are cached, and you pay for exact usage, not machines.
dagger.io/blog/dagger-for-gi…
Announcing Dagger for GitHub.
Run the same checks before and after push. See results in your terminal and PR.
Cut out the middleman: just GitHub and Dagger Cloud.
Stop wasting compute: checks are cached, and you pay for exact usage, not machines.
dagger.io/blog/dagger-for-gi…
Dagger retweeted
it's still early days testing for me, but I predict that @GoEntire and @dagger_io are the next two parts of my stack that I'll use in every project. I need better agent integration with my code storage, safe automated merges, and CI runs that my agents can run anywhere
Agents reinvented how we produce code. It changed our tools and half of our workflow. It’s time for the other half to catch up.
Today, we’re shipping Entire: the Git forge for agent-human collaboration. We’ve built @GoEntire using Entire. Now we want to see what you'll build with it.
Here’s why and what’s different. 🧵