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
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.
Dagger retweeted
Guys I promise you, emulating Github Actions locally will not fix your CI. Stop doing this to yourselves.
Dagger retweeted
When I want to deep dive into what's happening in CI, I reach for @dagger_io (which is what I use in CI to deploy all the Workers, IaC things, and build 10+ docker images). Dagger provides traces so I can see where the time is being spent (and optimize CI times)
Dagger retweeted
Previously I'd run my entire release process through GitHub CI and one of the key things is GitHub CI would have all of my secrets for release signing. That just doesn't seem like a smart idea anymore. I'm moving my release process client-side. The only thing that matters is it's portable and that's easy enough to do with a Docker container.
Hey maybe I should use @dagger_io. That's a decent sales pitch for Dagger. Run portable, predictable processes client-side to ensure greater security. It's not that I think GitHub is inherently insecure. It's just with the rise of AI it's just getting scary.
Dagger retweeted
What if your CI had a lockfile?
dagger.io/changelog/#a-lockf…
Dagger retweeted
FYI. This week we're moving Dagger Cloud to Absurd by @mitsuhiko. Will share our experience if anyone's interested.
cc @marcosnils @matiaspan26