9 comments

  • colek421 hour ago
    We should probably be measuring deployable merges to main. The math just doesn&#x27;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.
    • dbworku1 hour ago
      Definitely agree that agent volume will push beyond pipelined CI. Most teams we’ve talked to are still working to get up to 100 PR&#x2F;hour.
  • esafak6 minutes ago
    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.
  • jstrasner1 hour ago
    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?
    • yonasb1 hour ago
      We use Mastra to run the agents in our CI harness. It&#x27;s been great for being able to swap out models easily. More details here <a href="https:&#x2F;&#x2F;starsling.dev&#x2F;blog&#x2F;agent-loop">https:&#x2F;&#x2F;starsling.dev&#x2F;blog&#x2F;agent-loop</a>.
  • buildwrangler1 hour ago
    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.
    • yonasb5 minutes ago
      Thank you! Yeah most teams don&#x27;t have someone with your experience so they end up with really inefficient GHA setups. Doing our best to help!
    • dbworku50 minutes ago
      Thanks! It’s an unappreciated bottleneck so we feel your pain.
  • sochs0 minutes ago
    Off topic but every time I read a name like &quot;Star Sling&quot; I get excited to see another space startup tackling a difficult challenge; and so when it turns out to be CI for agents, it&#x27;s a letdown and an annoyance. Idk, this project seems cool, but maybe pick a less pretentious name.
  • dotmike2 hours ago
    Congrats on the launch! Will give it a run. Why is your CI fast? Curious to hear the technical details
    • dbworku1 hour ago
      Our primary difference is self-improving PRs from continuously analyzing the telemetry from your CI. Most folks just sell fast hardware and are happy to charge you for jobs that don&#x27;t saturate the host.<p>In our examples with open-source repos above you&#x27;ll see that most of speedups that lead to a 10X speedup come from code changes or optimizations.
  • gkoberger2 hours ago
    Congrats on the launch! These benchmarks look really great, can&#x27;t wait to start using this.<p>What are some of the most interesting things the AI has caught + fixed so far?
    • dbworku2 hours ago
      Oof. It&#x27;s hard to pick one! I like the subtle fixes like swapping sleeps in tests with DB readiness checks or pinpointing a single long running test causing a shard to run slow.
  • d-sanoj1 hour ago
    Congrats on the launch. This seems interesting.
    • yonasb1 hour ago
      Thanks! If CI is on your priorities list, give us a shot.
  • kinfish1 hour ago
    congrats on the launch!