Faster Rapids Builds, Plus an Optional Build Cache
Deploys start seconds after a build finishes, builds get more CPU headroom, and you can keep a build cache per container to speed up the next build.
What's changed
- A finished build now starts its deploy within seconds instead of waiting up to a minute
- Builds get twice the CPU headroom, so toolchains that use every core, such as Next.js, finish sooner
- Dockerfile builds now run on a new builder, with no change needed on your side
- Turn on Keep the build cache for a container that builds from a Dockerfile to reuse its image layers and cache mounts, so later builds finish faster; the API field is build_cache_enabled
- The cache only ever saves time: if it is not available the build runs without it, and a cache unused for 14 days is removed