Preview environment docker build caching

It seems like since every preview environment is its own blueprint/environment, that means every service in a preview environment has its initial deploy every time a new new pull request is opened. Does this mean that any service in a new preview environment isn’t able to take advantage of any sort of build caching as each service is built from scratch?

If so, this seems like a missed opportunity since the initial build is quite slow (ie downloading ruby or npm dependencies every time, even if a package lock file has not changed). Is there any possible way to get preview environments using parts of a build cache when a new PR is opened?

1 Like

Currently, there is no caching across different services, including the preview service and its parent service.
I think your suggestion makes sense. I create a feature request for it Docker build cache for preview environment services | Feature Requests | Render

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.