-
Notifications
You must be signed in to change notification settings - Fork 21
Cache always empty on Deploy Preview builds #22
Comments
I'm not 100% sure; I would expect that a deploy preview would use the cache, but there's a possibility that this is done to prevent conflicts since the branches won't match cc @ehmicky — is this intended, or should I file a buildbot bug? |
I think I've heard there were some reasons why deploy preview caches are sometimes empty, partially intended, but also partially due to existing issues. I would suggest asking the buildbot team. |
yeah, that's related. I was able to duplicate on a non-Gatsby site as well, so something’s going on for sure |
Hi, the build times pretty much the same with or without build plugin. Any advice? thank you |
|
Exciting update: this was an upstream Netlify issue that has been fixed 🎉 Check out our Community post for more details: https://community.netlify.com/t/build-cache-is-now-updated-in-deploy-preview-builds/26344 |
thanks so much for the update @kaganjd! |
Hi! Big thanks for this plugin - it's helping to bring down the build time on our
develop
branch significantly.However, on Deploy Preview builds the cache seems to always be empty - even on repeat builds. Is this a know limitation of the plugin?
We were able to remove the re-install overhead of the plugin by following the steps in netlify/build#1134 - but the
yarn
command still takes ~1 minute on the Deploy Preview builds for some reason - compared to ~1 second on thedevelop
branch. (related?)Deploy Preview log on a repeat build:
The text was updated successfully, but these errors were encountered: