Depot

Nested virtualization is now on by default in every Depot CI sandbox. No extra config, no extra cost. The headline use case is the Android Emulator at native speed for tests, but it also opens up full VMs for end-to-end testing (a Kubernetes cluster, for example), QEMU/KVM workloads inside a job, and hypervisor development. https://lnkd.in/diCq5R5m

Just your weekly reminder that we saved developers 243,590 hours last week. ;)

I watched a developer do this six times in a row last week. Commit. Fail. Copy logs. Paste. Fix. Fail again. He was the slowest part of his own pipeline. Here is how Depot CI kills that loop entirely: Your coding agent gets Depot CI skills baked directly into it. Programmatic access to the full CI interface. So the workflow looks like this: 1. You prompt your agent to build a feature or fix a bug 2. The agent implements the change 3. Before committing anything, the agent triggers Depot CI runs with the local file changes 4. CI passes? Great. CI fails? The agent pulls the logs, figures out what broke, and fixes it 5. The agent can even SSH directly into the machine to debug something itself All of this happens before a single commit. By the time the code is committed and the PR is open, CI has already passed. No back and forth. No copying logs into a chat window like it's 2023. The agent already handled it. The key is giving your agent the right tools and rules. Bake in rules like "once you implement the change, use the Depot CI skill to validate your change passes CI in these workflow files." That's it. The agent does the rest. This is what "human on the loop" actually looks like. You're not babysitting the feedback cycle. You're reviewing code that already works. What's the most time you've wasted going back and forth between a failed CI run and your agent?

We’ve made over 100 million builds near instant, but that's only 30% of the CI pipeline. We’re now building the CI for the next era of software development. Here's how we’re doing it. Every CI job starts from absolute zero. Check out the code. Install dependencies. Rehydrate caches. Build. Test. Deploy. That front half repeats on every single job. I lived with it for years. Most teams still do. But when I broke down where the time actually goes, I couldn't unsee it. This isn't a speed problem. It's an architectural one. Traditional CI spins up a fresh VM every time. No state. No memory. You spend the first chunk of every build just getting back to where you were five minutes ago. With Depot CI, the runner already has the code checked out, dependencies installed, caches hydrated. It starts where the last one left off. No rebuilding from zero. In practice: - Node/TypeScript workflows: saving 20-40 seconds of setup when the lint check itself is 30 seconds. Job cut in half. - Java or Rust projects: saving three to ten minutes per build. Rust lint checks that take 30-40 seconds but need three minutes of plumbing to get there. Three minutes of setup for 40 seconds of actual work. Brutal. This isn't theory. Over 100 million builds processed at Depot, 2,000 to 3,000 running at any given minute. When a new team signs up, we make their builds exponentially faster within 30 minutes. Within two days, a real human reviews their builds and says, "Fix this, this, and this." That advice helps regardless of whether they stick with Depot. That setup time compounds across every job, every PR, every developer, every day. It's not one 30-second tax. It's thousands of them. We don't ship "trust me" performance. We benchmark it. Every time. What's the heaviest setup tax in your pipeline right now?

Depot Registry is OCI-compliant and can act as your primary registry, not just an ephemeral build bucket. Each org gets its own subdomain, custom repository names, retention by days or tag count, pull-through caching, and any OCI artifact up to 50GB. https://lnkd.in/eUkPrhyw

Kyle Galbraith on The Kubelist Podcast: "CI is sitting in this unique space where it can be the verification substrate of: can I trust this code? Is it high quality? Can it go to production?" https://lnkd.in/de8JU2iZ

We’ve made over 100 million builds near instant, but that's only 30% of the CI pipeline. We’re now building the CI for the next era of software development. Here's how we’re doing it. Every CI job starts from absolute zero. Check out the code. Install dependencies. Rehydrate caches. Build. Test. Deploy. That front half repeats on every single job. I lived with it for years. Most teams still do. But when I broke down where the time actually goes, I couldn't unsee it. This isn't a speed problem. It's an architectural one. Traditional CI spins up a fresh VM every time. No state. No memory. You spend the first chunk of every build just getting back to where you were five minutes ago. With Depot CI, the runner already has the code checked out, dependencies installed, caches hydrated. It starts where the last one left off. No rebuilding from zero. In practice: - Node/TypeScript workflows: saving 20-40 seconds of setup when the lint check itself is 30 seconds. Job cut in half. - Java or Rust projects: saving three to ten minutes per build. Rust lint checks that take 30-40 seconds but need three minutes of plumbing to get there. Three minutes of setup for 40 seconds of actual work. Brutal. This isn't theory. Over 100 million builds processed at Depot, 2,000 to 3,000 running at any given minute. When a new team signs up, we make their builds exponentially faster within 30 minutes. Within two days, a real human reviews their builds and says, "Fix this, this, and this." That advice helps regardless of whether they stick with Depot. That setup time compounds across every job, every PR, every developer, every day. It's not one 30-second tax. It's thousands of them. We don't ship "trust me" performance. We benchmark it. Every time. What's the heaviest setup tax in your pipeline right now?

April was a huge month bringing a steady stream of updates to Depot CI and a fresh 🚀. Check out the details 👇

🚀 Depot CI now supports secret and variable variants. Scope by repo, branch, workflow file, or environment. Branch and workflow scopes accept globs. Most specific match resolves at job start, and you can preview the resolution from the dashboard. https://lnkd.in/dBAk_P9W