Depot Code is now in private beta. It's the git host we wanted after three years accelerating everything downstream of source control: a diskless git server that stores content in S3 and scales horizontally. Regular git under the hood.
Depot CI and Sandbox workloads are now running on Depot Metal, our new 4th-gen compute platform. Benchmarks show them running 30% faster, with nothing to migrate. Built on bare-metal EC2 with microVMs and dedicated NVMe storage.
two test failures can look different and still represent the same failure pattern.
the hard part isn't collecting failures. it's knowing when two failures are actually the same.
iris goes deep on how failure fingerprinting filters out noisy data while preserving the pieces that
we just made snapshotting in depot ci blazing fast from 30 Mbps to 1 Gbps โก
probably going to bring this over to our sandbox sdk here shortly as well.
AI can generate code in seconds.
That doesn't mean the hard part is solved.
Someone still has to understand the code, review it, maintain it, and debug it months later.
Engineering guardrails like linting rules, reference tests, coding standards, and reviewable pull requests
New case study with @PlanetScale .
PlanetScale runs CI at massive scale. After moving their CI workloads to Depot, they cut CI time in half on many workloads, eliminated runner management, and stopped thinking about CI.
Read the full story:
We're pumped to be powering @pantsbuild for all of their CI ๐
"Depot hosted runners were exceptionally easy to set up, basically just a drop-in replacement for our GitHub hosted runners, but the performance and stability are substantially better."
You haven't manually re-run a job in weeks.
That's the feature.
When a Depot CI job fails, `depot ci diagnose` gives you the failed step and the error lines that matter. No log paging, no re-running just to see what broke.
`depot ci diagnose --run <run-id>`