Is there any way to compare the cached build/deploy config between two deployments? And what is cached, is it just the dependencies (ie, the node_modules folder) or more?
Context: We’re hitting a frustrating bug on our site - we have two Netlify ‘sites’ pointing at the same repo, which was initially set up to allow us to have a ‘develop’ branch as the default branch on one site (which can be password protected to hide sensitive WIP), and ‘master’ as the default on another (strictly for production-ready builds and split testing). Since then we’ve moved away from using ‘develop’ as a route to production, but this legacy arrangement persists since we find it useful.
The problem is that, at some point, the build/deploy cache has been cleared on the ‘develop’ site, and on builds on that site we see a strange bug - AFAIK the symptoms of the bug itself are not really relevant to the problem, but I’ve included steps to reproduce at the bottom of this post, in case it’s useful.
What is certain is that two nominally ‘identical’ builds (links below) from the same branch of our repo (master) are displaying different behaviour, and the only reliable difference that I can anticipate is the build/deploy cache on each site.
Furthermore, our repo doesn’t currently have a package-lock.json file, which is another clue that it’s likely a dependency discrepancy…
So fundamentally I think that’s the question - is there any way to retrieve the cached build/deploy data?
Steps To Reproduce Bug:
Browser must be Google Chrome on desktop (issue does not appear on Android GC nor macOS/iOS Safari, but I’m quite sure this isn’t a GC bug per se, rather an issue with one of the package dependencies in GC)