Closed gopivemula1 closed 3 years ago
Looks like react-scripts build
is failing. Maybe it has a verbose mode, so you can get more debug output?
Looks like
react-scripts build
is failing. Maybe it has a verbose mode, so you can get more debug output?
Hi @eirslett it runs with out errors in Mac, windows . Fails only in Jenkins.
I'm sorry, with this little information I am not able to help. Maybe it's a Linux issue.
@eirslett you can not simple say Linux issue and close it, you can help how to resolve this issue. I am facing the same issue after pushing my project code and try to build through jenkins. I spent 4 weeks of my time on POC based on this plugin, now what should I do if its failing to deploy in QA environment.
@eirslett you can not simple say Linux issue and close it, you can help how to resolve this issue.
I closed the issue because (to me) it looks like it's a react-scripts bug, and not a bug with this plugin.
It's an open source project that you can use for free, I made it voluntarily in my free time. I have no obligations to help anybody. But if you pay me an hourly rate and give me access to the Jenkins server, I can try to help you debug!
The output says Treating warnings as errors because process.env.CI = true.
You could try running CI=true npm run build
locally/on Mac and see if that reproduces the problem locally.
@eirslett you can not simple say Linux issue and close it, you can help how to resolve this issue. I am facing the same issue after pushing my project code and try to build through jenkins. I spent 4 weeks of my time on POC based on this plugin, now what should I do if its failing to deploy in QA environment.
@mkpasala this plugin is not working for Jenkins. I used docker and docker-compose to build and deploy my react and springboot as alternate solution.
[Pipeline] Start of Pipeline [Pipeline] node Running on Jenkins in /var/lib/jenkins/workspace/Testnet-pipeline [Pipeline] { [Pipeline] tool [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: No tool named maven3.8.4 found Finished: FAILURE
What do I do?
What do I do?
I don't think this is a problem with the frontend-maven-plugin. Looks like you're trying to use Maven 3.8.4 (configured in your build somewhere) but you haven't installed it on your Jenkins properly?
okay so i had been facing the same issue with a react-based application build that i was running on jenkins
[INFO] Treating warnings as errors because process.env.CI = true. [INFO] Most CI servers set it automatically.
here in your .env file you have to change process.env.CI = false if you want your project to compile in jenkins with warnings successfully. or else jenkins will always fail the build/pipeline
ref - https://stackoverflow.com/questions/52888214/how-to-set-environment-variable-in-react-js
Hey,
I am facing an issue with Jenkins
0:0 error Parsing error: No Babel config file detected for /home/jenkins/agent/workspace/.../.Either disable config file checking with requireConfigFile: false, or configure Babel so that it can find the config files
Also things are working fine with my localhost
I already tried multiple options but nothing works for me
Can anyone help me out with this issue
frontend-maven-plugin version: 1.12.0
Current Behaviour: when using this plugin to compile it is successful in local, however it fails jenkins pipeline.
pom.xml configuration
Log file:
Jenkins Logs: