4 ms·
AFAIK most orgs that use something like Azure DevOps pipelines for builds will deploy a VM Scale Set Agent Pool with the runner image. This provides layer cachi
by jiggawatts 4y ago
AFAIK most orgs that use something like Azure DevOps pipelines for builds will deploy a VM Scale Set Agent Pool with the runner image. This provides layer caching and incremental builds. Ref: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/scale-set-agents?view=azure-devops https://learn.microsoft.com/en-us/azure/devops/pipelines/age...
What’s the advantage of your platform over this?
- jacobwg 4y agoI haven't used Azure DevOps scale sets, but it looks similar, assuming it is orchestrating a persistent cache disk. If you're not using Azure DevOps, or even if you are, you can use `depot build` from any CI provider or from your local machine, anywhere you'd run `docker build` today, and the speed and cache are shared everywhere. And you don't need to configure any infrastructure. We also orchestrate both Intel and Arm machines depending on what type of build you need to do (or both for multi-platform). That can be important if you need to run on Arm in production, or if you have developers using new MacBooks. We're working on more Docker-specific features as well, we plan to directly integrate things like SBOMs, container signing, build analytics and insights for what happens inside the Docker build, etc into Depot, there are some interesting things we can do having control of the execution environment.