Buildkite retweeted
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
tbh, the safest setup may be going with a different system, like @buildkite and self host
0
1
3
276
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, nb, 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
1
4
6
671
Buildkite retweeted
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.
You need to be building loops around CI optimization and automatic test selection. You should be compute-neutral. Just use @buildkite.
7
2
78
8,289
Buildkite retweeted
What you really want is an easy to use, powerful, secure, well-thought out software layer and BYOC underneath. Guess what... that's Buildkite.
1
2
6
2,182
Buildkite retweeted
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.
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!
7
2
55
6,408
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 ff the horde?
That’s a wrap. Happy Halloween 💀
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 ff the horde?
That’s a wrap. Happy Halloween 💀
0
1
2
1,059
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 to close the trilogy.
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 to close the trilogy.
0
1
1
524
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.
“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.
0
1
1
370
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.
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.
0
0
3
321
Buildkite retweeted
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?
11
3
48
8,979
Buildkite retweeted
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!
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.
buildkite.com/resources/chan…
1
1
14
744
Buildkite retweeted
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.
5
4
48
5,555
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.
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.
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 t’s different. 🧵
0
7
26
1,893
The 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.
Caching is now generally available in Buildkite. Multiple techniques compounding together. The first of several new building blocks for faster, better CI.
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.
buildkite.com/resources/chan…
0
0
4
981
