Open trisquel87 opened 4 years ago
Does it work when running locally?
@eirslett yes, we don’t have any problem in local.
Try setting <installDirectory>
and <workingDirectory>
for every execution maybe?
Try setting
<installDirectory>
and<workingDirectory>
for every execution maybe?
@eirslett I have the same problem.
Is there any chance that the target
directory is wiped out between executions, somehow? Or the node binary ends up in the wrong directory somehow? Try logging into the CI server/into the build pipeline and checking its filesystem?
I had a issue running the plugin, but it was because plugin requires maven 3.1 and above.
Normal npm/node releases won’t work on Alpine or any musl-libc based distribution. I had to abandon Alpine at work because this plugin is in many of our projects.
Hello I'm having the same issue with gitlab ci @hermitmaster what are you using instead of Alpine?
@hyahyaoui Debian slim based images. Really, anything with glibc works fine.
@hermitmaster thanks :)
frontend-maven-plugin downloads a musl-based NodeJS since https://github.com/eirslett/frontend-maven-plugin/pull/853, so there should no longer be a need to install glibc (which adds quite a bit of disk usage to that otherwise tiny Alpine image, and I guess keeping it small is the point of using Alpine).
Hello,
we have a problem using the plugin (v1.9.1 or any other) in Bitbucket pipelines.
We have this pipeline:
The error that we have is:
The structure of our project is:
project |__alert-business |_pom.xml |__alert-util |_pom.xml |__alert-web |___pom.xml |__pom.xml
We have a react aplication with package.json inside one folder of alert-web subproject.
The aplication is compiling in local but not in the pipeline.
The pom.xml inside the alert-web subproject is:
`
We try to solve the error installing npm in the pipeline but we can't not compile the project. We also try to use others docker images for the pipeline but we have the same error.
Can you help us?
Thanks.