-
-
Notifications
You must be signed in to change notification settings - Fork 0
Why do checks keep failing? #23
Comments
I think this is a node issue. Netlify says it runs Maybe @zkamvar can help? (not super urgent but would ideally like to have this fixed before end of year) |
I also think it's a node issue. Specifically, I think it has to do with the cache that Netlify has (but can not tell how the cache is setup): For example, in this deploy that worked on November 30, things were built fine and it shows node working to build the dependencies and move everything into folders: https://app.netlify.com/sites/carpentries-org-preview/deploys/63877449d3e970000866bd15#L269-L291 Log showing node installation
However, recent deploys do not go through all those steps and instead looks for a cache and attempts to restore with no messages: https://app.netlify.com/sites/carpentries-org-preview/deploys/6387cae43cff26000870e9d4#L139-L141
|
I am rerunning https://app.netlify.com/sites/carpentries-org-preview/deploys/639777eb8a4c33301fac0939 while resetting the cache and it looks to be running, so it is a cache issue. I get a feeling that the JS modules in here are not set up in a typical fashion (probably to facilitate offline development). |
Also, FWIW, unless something changed, we deploy PR previews through Netlify and https://beta.carpentries.org/ through AWS. The builds from Netlify will go to https://carpentries-org-preview.netlify.app/. I believe it has something to do with registration of the carpentries domain being tied to CloudFront and being unable to serve a subdomain from another service, but that's an area that I'm still unfamiliar with. |
I know what's happening: The cache restore for node modules does not consider the postinstall script in our package.json: beta.carpentries.org/package.json Lines 6 to 8 in 915e512
When it restore the cache, it's literally just moving the cached files over to Our solution likely is to run the postinstall script in |
This explains a bit of the logic behind the caching as well: netlify/build-image#714 (comment) I suspect that the postinstall script that we have right now is a desire path that has not been paved in npm. |
This will ensure that the node modules are added to the right place before the site is built. This will fix #23
Note: the path I took to get here:
|
Build checks on PRs keep failing. Here's an example explanation from the Netlify logs (private link). I don't know what this means or how to fix it.
The text was updated successfully, but these errors were encountered: