2025-07-25
1 小时 6 分钟Welcome to Changelog and Friends, a weekly talk show about oversharing shower habits.
Thanks to our partners at Fly.io, the public cloud built for developers who ship.
We love Fly.
You might too.
Learn more at Fly.io.
OK, let's play.
well friends it's all about faster builds teams with faster builds ship faster and win over the competition it's just science and i'm here with kyle gallbraith co-founder and ceo of depot okay so kyle based on the premise that most teams want faster builds that's probably a truth
if they're using ci provider for their stock configuration or github actions are they wrong are they not getting the fastest builds possible I would take it a step further and say
if you're using any CI provider with just the basic things that they give you,
which is if you think about a CI provider.
It is, in essence, a lowest common denominator, generic VM.
And then you're left to your own devices to essentially configure that VM and configure your build pipeline,
effectively pushing down to you, the developer,
the responsibility of optimizing and making those builds fast, making them fast,
making them secure, making them cost-effective, like all pushed down to you.
The problem with modern day CI providers is There's still a set of features and a set of capabilities that a CI provider could give a developer that makes their builds more performant out of the box,
makes their builds more cost effective out of the box, and more secure out of the box.
I think a lot of folks adopt GitHub Actions for its ease of implementation and being close to where their source code already lives inside of GitHub.
And they do care about build performance, and they do put in the work to optimize those builds.
But fundamentally, CI providers today don't prioritize performance.