You deserve better CI. Cursor, OpenAI, Anthropic, Nvidia, Uber, Airbnb, Canva, Bazel, vLLM, Amp, Entire, Bun, Rails + more run their CI on Buildkite.
Joined June 2013
- Tweets3K
- Following77
- Followers4.1K
- Likes1.6K
The question isn’t how fast single builds run. It’s whether your CI gets faster or slower as your work compounds and multiplies.
More compute might buy you time... but it doesn’t change the answer.
We are either going to need more compute, or better CI.
AI driven dev means more code/tests and more frequent changes trying to merge and deploy to production.
E.g. 10× the changes × 5× the test suite cost = 50× the compute (and higher peak compute demand due to parallelism).
And that's before you rebase a few times to keep up with the fast moving trunk, then battle a merge queue due to flaky tests.
There are a few things everyone should be doing. First off, you make your test suites leaner and faster. High signal units, massive parallelism, thoughtful end-to-ends.
What needs to come next is compute reduction. You should only run the tests that relate to the change you are testing. The next step is getting even smarter. Models can be used to predict which subset of the related tests are most predictive of failure which lets you get to the failure fast and avoid unneeded subsequent test runs.
Buildkite retweeted
All this talk about using only end-to-end tests for AI-written code makes me think the real winner of the AI race is going to be Buildkite.
Buildkite retweeted
i'm with this guy. just use buildkite, it's wonderful. and if you're still getting crushed by CI go fix your test and build pass
Buildkite retweeted
Continue to love being on the @buildkite platform, as I see another GitHub Actions incident this morning. If you haven't thought of going in that direction, you should...
Buildkite retweeted
I love buildkite.
Same workflow file, different agents. Run your existing GitHub Actions workflows on Buildkite's Mac fleet. No rewrite. Try now.
Read more: buildkite.com/resources/blog…
Same workflow file, different agents. Run your existing GitHub Actions workflows on Buildkite's Mac fleet. No rewrite. Try now.
Read more: buildkite.com/resources/blog…
One for every build status you've ever felt personally.
Build Buddies, coming soon: shop.buildkite.com/?utm_sour…
Today, @SpaceXSI released the Origin App Marketplace. The same CI setup used by @cursor_ai to build Origin is now available to you.
Our native Buildkite integration is included alongside key industry heavyweights such as @linear, @vercel and more.
Built by Cursor. Built on Buildkite.
Buildkite retweeted
Mac orbs are in beta (ampcode.com/morbs)
Our team has been iterating a lot on our Mac/iOS app primarily in orbs; I’ve often had an orb thread push the changes to my iPhone using a runner on my Mac, but @buildkite preflight and now mac orbs allow agents to test their changes on Mac in a remote environment
xitter.cf/toolmantim/status/2095…
Being able to cut per-orb builds of the @AmpCode iOS and Mac app is incredible. Just tested and shipped an updated thread TOC button in Swift from my phone, with multiple rounds of fine tuning the UI. Now we gotta figure out how to generalise this for all app builders!
Buildkite retweeted
Watch Paul's full talk from Open House Australia 2026: youtube.com/watch?v=wxVWByMP…
Buildkite retweeted
Fast, flexible, economical. ⚙️
@buildkite ingests a trillion test executions a year. Paul Annesley on why they chose ClickHouse, and specifically ClickHouse Cloud, at Open House Australia 2026 👇
Start free with $300 in ClickHouse Cloud credits → clickhou.se/4hCzMjW
EXTRA! EXTRA! READ ALL ABOUT IT!
The Morning Build, Vol. 1 is out. A real, printed newspaper, hot off the press and on the streets of SF this week.
Didn't snag a copy? better.ci/vol-1
#SFTechWeek
Buildkite retweeted
i just automated our release and QA process!
using Grok Bot i made two Team Bots: sandcastle, my release manager, and poteto, my engineer bot. i added them to Slack and made a new channel for managing releases.
first i tell sandcastle that i want to do a cut. it'll DM all the contributors with links to their PRs so they know what goes in the next release and can DM the bot back if they have any blockers or objections.
sandcastle then kicks off the build, watches it automatically, and starts up an automated fuzz swarm. usually this is 10+ agents running on Grok 4.7 xhigh to run the build, click around and use it like a real user (using our verification skills and feature map), some are directed while a few are "chaos monkey" clicking things randomly to see what breaks.
whenever it finds an issue, i tell it to @ mention my engineer bot poteto, to spin up a Cursor Project to own triaging and fixing all the high pri issues. depending on the severity i may ask it to cherry pick the fix into our release branch and cut a patch release, or if it's a pre-existing issue i still fix it but include in the next release instead
that's one more tedious task that Grok Bot now handles for our team
Buildkite retweeted
I just realized I can solve all my problems by moving CI from GitHub actions using Namespace actions, over to buildkite.
Namespace devboxes are still essential to my workflow so all agents have mac machines to compile and test on. This change would only be so I stop hitting the stupid GitHub actions limit when I'm not even using their compute.
September was our largest month for throughput: 2,140,620,094 CI jobs were run across the month in total.
That's up 26% over August, and works out to about 826 jobs every second for the whole month. It's 4.5x our number from a year ago, and roughly double what we ran in March 2026.
Together those jobs ran for 6.95B minutes, which is about 13,200 years of compute in one month 🤯
September was our largest month for throughput: 2,140,620,094 CI jobs were run across the month in total.
That's up 26% over August, and works out to about 826 jobs every second for the whole month. It's 4.5x our number from a year ago, and roughly double what we ran in March 2026.
Together those jobs ran for 6.95B minutes, which is about 13,200 years of compute in one month 🤯