Buildkite

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

[Buildkite @buildkite]

💯

[Lachlan Donald @lox]

@manny4c We use and love @AmpCode at @buildkite

[misker @misker76288684]

@danlovesproofs 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

[Buildkite @buildkite]

We're excited to support both @evilmartians and @rails for this months SFRuby conf! 💚

[San Francisco Ruby Conference, Nov 10-12, 2026 @sfrubyconf]

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: https://t.co/jeTskNdI1k

[Buildkite @buildkite]

@supezen 👋��

[Pres Mihaylov @PreslavMihaylov]

@nateberkopec @buildkite Can confirm buildkite team is dope

[Nate Berkopec @nateberkopec]

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.

[Léonard @synthe102]

@dshaw Buildkite is doing wonders for me. Very happy with it.

[Nate Berkopec @nateberkopec]

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

[Nate Berkopec @nateberkopec]

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.

[Buildkite @buildkite]

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 💀

[Nate Berkopec @nateberkopec]

@kushbhuwalka Just use Buildkite like everybody else

[Buildkite @buildkite]

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.

[Buildkite @buildkite]

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.

[Buildkite @buildkite]

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.

[Lachlan Donald @lox]

What I want to know from the 5 new CI and sandbox providers I see every day spruiking how they are x% cheaper than everyone else: What are your margins like? If you're a thin wrapper around someone else's compute, what is your actual plan to retain folks when the next provider undercuts you? How can you convince customers you'll actually be here in 12 months and won't go broke or lose their data?

[Buildkite @buildkite]

@dagger_io @lox @ibuildthecloud @threadreaderapp Unroll pls ☺️

[Fred Lohner @fredloh]

The first test of this is looking very promising for us. Will report back as we scale this out across all our builds. Would recommend!

[Thomas Dohmke @ashtom]

I love the pull request. But reviewing agent-written code needs a loop. With Trails, evals feed the next round of agent work. Sessions, code changes, and CI checks from @buildkite and @depotdev stay together.

[Buildkite @buildkite]

Entire already runs its own CI on @buildkite. As of today, every team on @GoEntire can.

Push → build → check on the Trail.

Congrats @ashtom and the Entire team. Now every team on Entire has access to the CI orchestration platform frontier AI labs rely on to build the next wave of pioneering software.

[Thomas Dohmke @ashtom]

Agents reinvented how we produce code. It changed our tools and half of our workflow. It’s time for the other half to catch up.
Today, we’re shipping Entire: the Git forge for agent-human collaboration. We’ve built @GoEntire using Entire. Now we want to see what you'll build with it.

Here’s why and what’s different. 🧵