Open jtnord opened 11 months ago
wow, pretty awful imo, yarn
is more sensible in that regard.
I think the pom should be configured to use npm install
by default and if the environment value CI
is set then it should run npm ci
.
Otherwise every mvn install
will just wipe node modules which could have horrific performance impacts, (especially for people on windows where npm is slower)
but that may not work with people who do local releases.
Jenkins and plugins versions report
Environment
```text Paste the output here ```What Operating System are you using (both controller, and any agents involved in the problem)?
N/A
Reproduction steps
Expected Results
they are identical, any build can be cloned from SCM and the rebuilt by using defined versions of dependencies
Actual Results
there are changes. builds in CI and locally use the latest that they resolve
Anything else?
the build is using
npm install
and notnpm ci
the pom should be configured to use
npm ci
by default and if/when things are updated a developer should runnpm install
locally and then commit the changes to thepackage-lock.json
see https://github.com/jenkinsci/bom/pull/2121#issuecomment-1571752616 and https://github.com/jenkinsci/bootstrap5-api-plugin/pull/220