Buildkite
@buildkite
You deserve better CI. Cursor, OpenAI, Anthropic, Nvidia, Uber, Airbnb, Canva, Bazel, vLLM, Amp, Entire, Bun, Rails + more run their CI on Buildkite.
78 Following4.1K Followers3K Posts
- Buildkite@buildkiteLights. 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.
003165 - Buildkite@buildkiteBuildkiteRT @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?0306
- Buildkite@buildkiteBuildkiteRT @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!Lachlan Donald @loxWe've shipped Buildkite Cache, the first of several building blocks we're putting in place to make CI radically faster. We've learnt a lot from how the fastest companies in the world run their CI. Great caching isn't just one technique, it's several working together: what you reuse, where it lives, and which work you can avoid doing in the first place. We're starting with a save and restore primitive to control cached files across jobs, on hosted or self-hosted agents. You choose what goes into the cache key, when to fall back to an older entry, and which builds can share the cache. There's a lot more coming.0108
We've shipped Buildkite Cache, the first of several building blocks we're putting in place to make CI radically faster. We've learnt a lot from how the fastest companies in the world run their CI. Great caching isn't just one technique, it's several working together: what you reuse, where it lives, and which work you can avoid doing in the first place. We're starting with a save and restore primitive to control cached files across jobs, on hosted or self-hosted agents. You choose what goes into the cache key, when to fall back to an older entry, and which builds can share the cache. There's a lot more coming.73575.7K- Buildkite@buildkiteBuildkiteRT @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.0406
- Buildkite@buildkiteEntire 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 @ashtomAgents 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. 🧵07251.8K
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. 🧵103101728174K- Buildkite@buildkiteThe fastest step is the one you never need to run. Caching is now generally available in Buildkite. Multiple techniques compounding together. The first of several new building blocks for faster, better CI.Lachlan Donald @loxWe've shipped Buildkite Cache, the first of several building blocks we're putting in place to make CI radically faster. We've learnt a lot from how the fastest companies in the world run their CI. Great caching isn't just one technique, it's several working together: what you reuse, where it lives, and which work you can avoid doing in the first place. We're starting with a save and restore primitive to control cached files across jobs, on hosted or self-hosted agents. You choose what goes into the cache key, when to fall back to an older entry, and which builds can share the cache. There's a lot more coming.004925
- Buildkite@buildkiteThe 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.Lachlan Donald @loxWe 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.001382
- 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.214788K
- Buildkite@buildkiteBuildkiteRT @snoopy_dot_jpg: @lox @CraigBarrDev 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 pass01010
- Buildkite@buildkiteBuildkiteRT @michaelhedgpeth: 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...01010
- Buildkite@buildkiteBuildkiteRT @ItsCynnamoroll: I love buildkite.Buildkite @buildkiteSame workflow file, different agents. Run your existing GitHub Actions workflows on Buildkite's Mac fleet. No rewrite. Try now. Read more:01011
- Buildkite@buildkiteSame workflow file, different agents. Run your existing GitHub Actions workflows on Buildkite's Mac fleet. No rewrite. Try now. Read more:002556
- Buildkite@buildkiteToday, @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.Cursor @cursor_aiOrigin, Cursor’s code hosting platform, now supports over 20 integrations. Connect your repos to tools for CI, deployments, code review, security, monitoring, and project management.015646
- Buildkite@buildkiteBuildkiteRT @cursor_ai: Origin, Cursor’s code hosting platform, now supports over 20 integrations. Connect your repos to tools for CI, deployments, code review, security, monitoring, and project management.013609
- Buildkite@buildkiteBuildkiteRT @0xBrettj: Mac orbs are in beta ( 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 environment01014
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!
62612.5K- Show more posts
