Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
Ubuntu 16.04 LTS
Docker Server Version: 17.03.1-ce
using: jenkinsci/blueocean:latest
Description
Build step fails when using exact syntax as the NodeJS plugin wiki page at https://plugins.jenkins.io/nodejs
tools {
nodejs 'name'
}
sh 'npm install' is called the output from Jenkins the result is:
+ npm install
env: 'node': No such file or directory
script returned exit code 127
Docker exec on npm produces the exact same error:
/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node/bin/npm env: 'node': No such file or directory
Attachments
Issue Links
- depends on
-
JENKINS-26583 Env-inject plugin suppress variables contributed by extension points
-
- Resolved
-
- duplicates
-
JENKINS-27170 "Provide Node & npm bin/ folder to PATH" not working for "npm install"
-
- Closed
-
- is duplicated by
-
JENKINS-44091 Use NodeJS in Pipeline
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Build step fails when using exact syntax as the NodeJS plugin wiki page at [https://plugins.jenkins.io/nodejs] tools \{ nodejs 'version_name' } sh 'npm install' is called the output from Jenkins the result is: + npm install env: 'node': No such file or directory script returned exit code 127 Docker exec on npm produces the exact same error: /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node/bin/npm env: 'node': No such file or directory |
Build step fails when using exact syntax as the NodeJS plugin wiki page at [https://plugins.jenkins.io/nodejs] tools \{ nodejs 'name' } sh 'npm install' is called the output from Jenkins the result is: + npm install env: 'node': No such file or directory script returned exit code 127 Docker exec on npm produces the exact same error: /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node/bin/npm env: 'node': No such file or directory |
Link |
This issue duplicates |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue depends on |
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Open [ 1 ] |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Description |
Build step fails when using exact syntax as the NodeJS plugin wiki page at [https://plugins.jenkins.io/nodejs] tools \{ nodejs 'name' } sh 'npm install' is called the output from Jenkins the result is: + npm install env: 'node': No such file or directory script returned exit code 127 Docker exec on npm produces the exact same error: /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node/bin/npm env: 'node': No such file or directory |
Build step fails when using exact syntax as the NodeJS plugin wiki page at [https://plugins.jenkins.io/nodejs] {code} tools { nodejs 'name' } {code} sh 'npm install' is called the output from Jenkins the result is: {code} + npm install env: 'node': No such file or directory script returned exit code 127 {code} Docker exec on npm produces the exact same error: {noformat} /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node/bin/npm env: 'node': No such file or directory {noformat} |
Link |
This issue is duplicated by |
Resolution | Duplicate [ 3 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Attachment | screenshot-1.png [ 45152 ] |
Resolution | Won't Fix [ 2 ] | |
Status | Reopened [ 4 ] | Closed [ 6 ] |
This sound like duplicate of one of these
JENKINS-27170JENKINS-41762JENKINS-42323JENKINS-41857JENKINS-43066JENKINS-43156Do 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)