-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins 2.32.3 (LTS)
a lot of other plugins
NodeJS Plugin 1.1.3
I have updated the NodeJS Plugin yesterday from version 0.2.2 to 1.1.3 on our Jenkins instance. Afterwards I upgraded Jenkins from 2.32.1 to 2.32.3.
We have several FreeStyle jobs that are building with Node.js with the following configuration:
- set up the path with the corresponding Node.js version, using no specific nprmrc file:
- then have a shell execution build step running some node or npm commands, you could test with
node -version
After restart of Jenkins all of our jobs fail, it seems like the plugin is not able to prepare the build environment correctly.
And here is the console output:
- duplicates
-
-
- Closed
-
[JENKINS-43156] Provide Node and NPM to Path does not work
| Attachment | New: image-2017-03-28-11-09-14-187.png [ 36800 ] |
| Description |
Original:
I have updated the NodeJS Plugin yesterday from version 0.2.2 to 1.1.3 on our Jenkins instance. Afterwards I upgraded Jenkins from 2.32.1 to 2.32.3. We have several FreeStyle jobs that are building with Node.js with the following configuration: * set up the path with the corresponding Node.js version, using no specific nprmrc file: !Screenshot from 2017-03-28 10-45-41.png! * then have a shell execution build step running some node or npm commands, you could test with {code:java} node -version{code} After restart of Jenkins all of our jobs fail, it seems like the plugin is not able to prepare the build environment correctly. |
New:
I have updated the NodeJS Plugin yesterday from version 0.2.2 to 1.1.3 on our Jenkins instance. Afterwards I upgraded Jenkins from 2.32.1 to 2.32.3. We have several FreeStyle jobs that are building with Node.js with the following configuration: * set up the path with the corresponding Node.js version, using no specific nprmrc file: !Screenshot from 2017-03-28 10-45-41.png! * then have a shell execution build step running some node or npm commands, you could test with {code:java} node -version{code} After restart of Jenkins all of our jobs fail, it seems like the plugin is not able to prepare the build environment correctly. And here is the console output: !image-2017-03-28-11-09-14-187.png! |
| Link |
New:
This issue duplicates |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
@nfalco: OK, sorry for missing the note and all these issues. I can understand your frustration. Will try to build your extra branch.
FYI, I was able to workaround this issue by putting a dummy nodejs script execution task before the shell task that was executing npm.
tomer liberman
added a comment - jonathonmg 10x! did the trick for me as well
This sound like duplicate of one of these
JENKINS-27170JENKINS-41762JENKINS-42323JENKINS-41857JENKINS-43066Do you have EnvInject plugin installed?
If yes than you fall in
JENKINS-26583The workaround reported in our wiki page is remove EnvInject plugin, or make a custom build of workaround-26583 branch. (this branch will never merge into master, it's a EnvInject plugin issue not nodejs)