our problem persists, but with a twist.
I am developing on a Linux system and am unable to build nor deploy locally.
My colleague uses a Mac with the same node, npm, gatsby, gatsby-cli versions az I am using, and is able to build but not deploy locally.
These are the versions he is using:
- node: 10.16.3
- npm: 6.13.1
- gatsby-cli: 2.8.14
- gatsby: 2.18.5
Can the different operating systems have anything to do with the different result?
I set the node and npm versions in the netlify.toml file, so the build also runs with these versions.
We have not been able to push a single commit that netlify was able to build and deploy ever since I opened this thread.
My colleague has been able to deploy from a local netlify-cli. That is what saved us.
For some reason neither of us understand, netlify will not deploy successfully since the day I made the changes to our deploy context settings (maybe doesn’t have anything to do with our problem, but it’s the only thing that changed when deploys started failing).
Since then we have tried many versions of gatsby, npm and node, updated gastby plugins… downgraded plugins to versions used when netlify deployed successfully… no luck.
Our newest error is:
chmod: cannot access ‘/opt/buildhome/.gimme_cache’: No such file or directory