Deploying new projects started failing on Netlify. Checking the logs I see something that was not in the logs on previous successful deploys:
Treating warnings as errors because process.env.CI = true.
Most CI servers set it automatically.
Failed to compile.
How can I fix my build?
You need to have CI to be false during your build command.
Go to: https://app.netlify.com/sites/mysales-krohne/settings/deploys > Build command and change it to:
CI=false npm run build
Now, rebuild your deployment. Should be no problem anymore.
If you want to know more about this. I wrote a blog on this topic: https://360techexplorer.com/treating-warnings-as-errors-because-process-env-ci-true-vercel-netlify-jenkins-etc/
Once your deployment is failed, go to Deploys -> Deployment Settings.
There you will see Environment tab. Then click Environment Variables -> Edit Variables
Redeploy with clearing cache.
On June 15 2020 Netlify made a configuration change "adding the environment variable CI to build environments, with the value of true." In your Build and Deploy settings on Netlify change your build command to CI= npm run build. This will prevent Netlify from treating warnings as errors. More discussion on this issue can be found in Netlify's forums.
Simply change the build command to:
CI= yarn build
or
CI= npm build
Like the other posts said, it is due to the CI, so any warning will stop the build. The lines above just means, setting the CI variable to nothing, and then start the command yarn build.
You should put CI='' npm run build
in your build settings.
See error below: https://docs.netlify.com/configure-builds/troubleshooting-tips/#build-fails-on-warning-message
But its better to correct the warnings...
Go to Deployment settings then Environment Variable after that click Edit set key: CI value: false
In Build setting let it be only yarn build or npm run build as it is in default settings no need to add CI=yarn build or CI=npm build
I found that everyone telling us to set the CI variable to false, but warning is something we should care about right? After all I see most of the CI servers implement such functionality, that I believe serve some purpose, maybe treating warnings as errors is just one of them. So instead of disabling such functionality, I think it's better to check whether you want to take these warnings in your deployed app or not. If it's something that you are expecting, for example lint warnings, then just configure your lint rules configuration or disable the lint checking on build phase, set it as separated step in the pipeline and you can set the CI variable to false on this specific stage. It feels safer than set the variable to false on the whole process if you are using for example azure static web apps deploy action
Sometimes even after setting
CI = yarn build or npm build command
the build fails.
In my case, I ran the build command on my local machine and there was an error with an import which was not being displayed in netlify console.
So If the build is failing then run it once on your local machine this will notify of any errors.
I was looking for a solution to fix this in Gitlab's CI and this is what worked for me in .gitlab.yml
...
default:
before_script:
- CI=false yarn build
...
Redeploy again after deleting your site from netlify
Use the command npm run build and not yarn build
Don't try to rename your website name when deploy process is going on to avoid errors
