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.7K
- Following207
- Followers7.4K
- Likes1.3K
Pinned Tweet
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
🧵
Dagger retweeted
exciting :D we love dagger
(though we barely know her)
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
If you haven't already, you should check out dagger (or have your agent check it out). If you have already, give 1.0 another try. So many improvements packed into it. We've addressed a big ask from many users: run your CI for you. And it's super cheap. Give it a shot!
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
The time has come. Too many organisations fixed to github infrastructure, github actions. Blocking releases to production. Even when you run your own github runners still the github actions fail. I seriously recommend organisations, tech leaders and influences to take a look at dagger. Its absolutely game changing. Unblock your agents and remove dependency on 3rd party infrastructure and ci costs!
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
Dagger is one of the sickest technologies I've seen in the recent years. It powers all our CI at TypeSafe! Can't recommend it enough
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
I've been following and testing Dagger from day one (years ago 👴).
I can confidently say that 1.0 is the real deal, and I'm lucky that it's right on time to be a core piece of my new startup's coding factory.
Do yourself a favor, time to switch to third-generation CI! 🔥🤖🔥
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 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
All software should have a similar prompt on their website, similar to @dagger_io, for fast setup and tire-kicking.
Dagger retweeted
So. We've been busy and will make a few announcements soon... Can you guess from the Changelog? 🤫😇
dagger.io/changelog
Dagger retweeted
In the beginning, there was the nightly build.
Then came agile, and the engineer said: “I must build and test more often.” And there was Jenkins, and the engineer saw that it was good.
Then came the pull request, and the engineer said: “I must check many contributions from many people.” And there was GitHub Actions, and the engineer saw that it was good.
Then came the coding agent, and the engineer said: “Oh boy…”
Dagger retweeted
Fellow systems engineering nerds! I’m giving a talk at Unfortunately Computers on November 12th in San Francisco.
Surprise! It's about the future of CI. Expect live demos 😇
Space is limited, sign up here to join me:
unfortunatelycomputers.com/e…
Thanks @recallai for hosting!
Dagger retweeted
For my next rant about CI, what should I talk about?
37%The end of self-hosted CI
26%Why all CI pricing sucks
13%CI & codegen
24%CI local execution
78 votes • Final results Dagger retweeted
CI stands for "continuous integration". But integration is actually a discrete event! So "continuous" just means "more frequent", the same way HD means "more pixels".
Now, with agents, integration is getting a whole lot more continuous... I guess this is CI's 4K moment? 😛
Dagger retweeted
“CI workloads are dumb, and running dumb workloads is wasteful. When your architecture boils down to “run shell scripts on VMs”, your scaling options are limited: more VMs or bigger VMs. This amounts to throwing money at the problem […]” many good takes here!
At @dagger_io we're building this scheduler, and the software stack to leverage it in your CI.
See dagger.io/blog/the-great-ci-…
Dagger retweeted
At @dagger_io we're building this scheduler, and the software stack to leverage it in your CI.
See dagger.io/blog/the-great-ci-…
Dagger retweeted
CI will continue to be a bottleneck for most orgs unless there's a true investment in rebuilding the factory with the right primitives. We've been working on it for the past 5 years @dagger_io.
Bigger machines won't fix your CI.
Dagger retweeted
Solomon was ahead of the curve with creating Docker and is ahead again. The discipline associated with (fast) automated testing applied today is a major contributor to the difference between 1x and 100x.
The potential difference between utter failure and spectacular success.
Dagger retweeted
Test workloads are build workloads; test bottlenecks are build bottlenecks.
It's time for a new kind of scheduler, that can run all our builds and tests as an integrated workload rather than dislocated siloes.
Then we'll wonder how we ever tolerated CI this slow and wasteful.
