Hello!
I have following configuration for pipeline:
image: node:latest pipelines: default: - step: script: # Modify the commands below to build your repository. - npm install - npm run build
Build fails if any warnings present.
Creating an optimized production build... Failed to compile. When process.env.CI = true, warnings are treated as failures. Most CI servers set this automatically.
How to handle this?
Hi Varnav, the build is failing as warnings are being treated as errors due to a certain environment variable being set/not set. In this case, it looks from your error message like the affected variable is 'process.env.CI' (which is now set to true). You may need to set that to false in order to allow compiling to pass even in the face of warnings being raised.
Let us know if this solved your issue!
Cheers,
Ana
Setting CI to false does not help, but unsetting it does help. But, unfortunately, this also supresses all warnings.
Looks like this is a create-react-app issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having a very tough time setting CI to false. Where do I do it from? I tried doing from Repo's environment variables , yet during my build run it is set as True.
I also tried doing it from the global settings at my team level or user level. Yet to no avail!
How do I set environment variable CI to false?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@varnav did you end up figuring out what the create-react-app issue was?
I am having the same issue during building, I wonder what solution you end up finding?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Shikha Chugh try writing the following, before running npm build as
- unset CI
- npm run build
This actually solved the issue for me
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"unset CI" worked for me and it still shows the warnings, which is what I wanted.
Thanks @soundar raj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.