10 comments

  • colek42 17 minutes ago

    We should probably be measuring deployable merges to main. The math just doesn't work for pipeline based CI as you add more agents.

    Three things matter.

    1 -- How many non-conflicting changes can actually be made at one time (Fan Out)

    2 -- How long a critical path takes

    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

    This is why most orgs cant get past about 12 PRs an hour.

  • jstrasner 22 minutes 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?

  • dotmike an hour ago

    Congrats on the launch! Will give it a run. Why is your CI fast? Curious to hear the technical details

    • dbworku an 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't saturate the host.

      In our examples with open-source repos above you'll see that most of speedups that lead to a 10X speedup come from code changes or optimizations.

  • gkoberger an hour ago

    Congrats on the launch! These benchmarks look really great, can't wait to start using this.

    What are some of the most interesting things the AI has caught + fixed so far?

    • dbworku an hour ago

      Oof. It'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-sanoj 27 minutes ago

    Congrats on the launch. This seems interesting.

    • yonasb 8 minutes ago

      Thanks! If CI is on your priorities list, give us a shot.

  • kinfish 22 minutes ago

    congrats on the launch!