Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
Jenkins 2.32.3 (LTS)
a lot of other plugins
NodeJS Plugin 1.1.3
Description
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:
Attachments
Issue Links
- duplicates
-
JENKINS-27170 "Provide Node & npm bin/ folder to PATH" not working for "npm install"
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | image-2017-03-28-11-09-14-187.png [ 36800 ] |
Description |
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. |
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 |
This issue duplicates |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |