We should probably be measuring deployable merges to main. The math just doesn't work for pipeline based CI as you add more agents.<p>Three things matter.<p>1 -- How many non-conflicting changes can actually be made at one time (Fan Out)<p>2 -- How long a critical path takes<p>3 -- How many times you have to run that critical path. Most orgs run it 2-3x, once before the PR in the agent loop, once in CI, and another in the MQ<p>This is why most orgs cant get past about 12 PRs an hour.
As you note, we can do those optimizations ourselves. The kind of person looking for CI runners is likely doing that already. What I value is speed, cost, scheduling delay, reliability, observability, local reproducibility, not using YAML... There is a lot of value to provide but workflow optimization is not where I would look.
So good! CI is still such a pain. Out of curiosity, do you use any open source harnesses under the hood or did you roll your own?
Congrats! I spent alot of time scaling really large and complex CI and integration testing builds so its great seeing a product that can help devs with this.
Thank you! Yeah most teams don't have someone with your experience so they end up with really inefficient GHA setups. Doing our best to help!
Thanks! It’s an unappreciated bottleneck so we feel your pain.
Off topic but every time I read a name like "Star Sling" I get excited to see another space startup tackling a difficult challenge; and so when it turns out to be CI for agents, it's a letdown and an annoyance. Idk, this project seems cool, but maybe pick a less pretentious name.
Congrats on the launch! Will give it a run. Why is your CI fast? Curious to hear the technical details
Congrats on the launch! These benchmarks look really great, can't wait to start using this.<p>What are some of the most interesting things the AI has caught + fixed so far?
Congrats on the launch. This seems interesting.
congrats on the launch!