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!
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?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot