I develop software for software developers to develop software - @Dagger_io - Docker Captain - Prev @Docker
France
Joined November 2010
- Tweets7K
- Following227
- Followers791
- Likes1.7K
Pinned Tweet
CI softwares are boring. Because they are most of the time dumb tasks runners.
But it doesn't have to be that way.
Forgot Jenkins, forgot GitHub Actions, and let's jump on the third generation of CI with @dagger_io 1.0 beta!
Come try it!
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…
Yves retweeted
How do I run Jest in CI and split the tests with --shard?
dagger.io/learn/jest-dagger/
Yves retweeted
@danielgafni has been using dagger for a long time at @typesafeai as our tool of choice for CICD and infra management.
Personally, I've been a complex-yaml-config hater for 15 years because you lose the expressiveness of code. to be clear i like yaml as serialization in most cases, but almost always prefer to store the construction of them in python files where you can do things like for loops and list comprehensions.
obviously, just keep that code simple and easy to read
this is how I do all my ML experiment configs, so it was an easy sell for our infra being this way too
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…
Yves retweeted
"When you peel off the layers of proprietary YAML and jargon, CI today boils down to running shell scripts on a server, and reading the logs. With such a primitive execution and data model, waste is everywhere, and it gets worse as you scale"
dagger.io/blog/dagger-10-bet…
Yves retweeted
After 5 years in v0, it's finally happening.. Dagger 1.0 is in beta and we need your help testing it.
If you've tried Dagger before, a lot has changed... We've been cooking.
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…
Yves 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…
Yves retweeted
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…
So. We've been busy and will make a few announcements soon... Can you guess from the Changelog? 🤫😇
dagger.io/changelog
Yves retweeted
So. We've been busy and will make a few announcements soon... Can you guess from the Changelog? 🤫😇
dagger.io/changelog
Yves 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…”
Yves 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!
Do you remember when CI was simply a hook on Subversion? (before Hudson became Jenkins for instance)
A lot of CI are still close to that, dumbly running tasks on push. In a better way for sure, but different, smarter? Not that much.
It's time for something new...
A quick animation of how my software factory is working to implement a feature (medium size, not a very obvious change, not a big one). Usually 10 agents are used for that.
It's using a mix of Claude and Codex, different models and efforts, as a way to optimise speed and result.
Yves 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 Yves 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? 😛
Yves 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-…
Yves 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.
🫣
Guys my team is mad at me, they think I'm talking about them 😅
To be clear I believe software factories are the future (yes the name is corny, get over it).
But there is one holdup: dagger.io/blog/the-great-ci-…
