
🫶🏻💚
I've got @synteq and @buildkite offering to sponsor compute to OSS projects with slow/expensive CI Hit me up and I'll see what I can do!

You deserve better CI. Cursor, OpenAI, Anthropic, Nvidia, Uber, Airbnb, Canva, Bazel, vLLM, Amp, Entire, Bun, Rails + more run their CI on Buildkite.

🫶🏻💚
I've got @synteq and @buildkite offering to sponsor compute to OSS projects with slow/expensive CI Hit me up and I'll see what I can do!

If you're an open-source project, hit up @buildkite and @depotdev. They are homies within the open-source community, very friendly folks.
Any OSS projects struggling with their CI speed/cost atm? May take a look tomorrow

Fair enough. Let me try and give you a better answer (and receipts). @buildkite runs CI for Shopify, OpenAI, Cursor and plenty of other fast-moving teams. Our own repo is roughly 2 million lines including tests, with over 2,500 PRs merged last month. We already use frontier models to build, test and review before push, plus a reviewer bot on the PR afterward. We still find bugs by executing the tests. Our suite takes hours without parallelism. We spread it across 110 nodes to get feedback in under 4 minutes. CI runs in the last few days caught: - Password resets stopping before security cleanup and audit logging. - A billing page crashing after an interface changed on another branch. - API validation raising an exception instead of returning 422. An agent could find those bugs by running the same tests. Great! Give it access to the infrastructure. Let it select tests, diagnose failures, fix code and maintain the pipeline. Good tests preserve requirements beyond the change the agent is currently making. When thousands of changes are coming together, you still need to execute them against the code you intend to ship. I’m keen on agentic CI too, it’s what we’re building. Better models can improve both the checks and how we run them. As software becomes more complex, it becomes more like an automated factory line, we need more deterministic automation where we can, not less.


lockfiles are new thing now and also reducing actions dependencies. tbh, the safest setup may be going with a different system, like @buildkite and self host

We're excited to support both @evilmartians and @rails for this months SFRuby conf! 💚
Join us in celebrating our biggest sponsor and @evilmartians client: @buildkite. Buildkite is a CI/CD platform that lets you run your pipelines on your own infrastructure, so you can scale builds and tests as far as you need without giving up control. It’s trusted by big teams, including Shopify, Airbnb, Uber, and Anthropic. Buildkite’s core app is built on Rails, and they’re longtime supporters of the Ruby community. Get to know Buildkite: buildkite.com/


Stop playing the game of switching CI to the “lowest cost” provider. That is a first order solution. You need to be building loops around CI optimization and automatic test selection. You should be compute-neutral. Just use @buildkite.


What you really want is an easy to use, powerful, secure, well-thought out software layer and BYOC underneath. Guess what... that's Buildkite.

Use a compute-neutral CI provider and run your own compute. That's what the big boys are doing, which is why they all run on @buildkite. Basically CI providers have turned into high-interest checking accounts or rewards credit cards. Each one makes a bunch of promises they can't keep to try to lock in customers, but it's all on borrowed time because their costs are not sustainable.
damn anyone solving for cheaper CI by any chance? our bills have gone crazy!

PART III: RE-RUN OF THE LIVING DEAD You know the ritual. Re-run failed jobs. Re-run all jobs. Still red. Stop feeding the undead. Buildkite finds flaky tests and quarantines them automatically, before the infection spreads to every build. Shouldn’t your team spend the week shipping vs. fighting off the horde? That’s a wrap. Happy Halloween 💀


PART II: BURIED Ancient curse, modern invoice. Your default repo CI rounds every partial minute up to a whole one, on every job. Fan out a few hundred jobs and the curse will bury you... Buildkite bills per second for hosted runners. Curse, lifted. No incantation necessary. Up next: the undead return to close the trilogy.

PART I: PARANORMAL AVAILABILITY “Waiting for a runner to pick up this job…” Is your CI ghosting you when it matters most? Now showing (in a queue near you). Stay seated. Something ancient rises tomorrow.

Lights. Camera. Actions? The unrest begins this week: a trilogy of CI horror that won’t stay buried rises in San Francisco. Rated U for Unreliable. Brought to you by @buildkite: the only CI that survives.