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
- depends on
-
JENKINS-26583 Env-inject plugin suppress variables contributed by extension points
-
- Resolved
-
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
[JENKINS-43593] NPM unable to locate node binary
| Description |
Original:
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 |
New:
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 |
New:
This issue duplicates |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
| Link |
New:
This issue depends on |
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
| Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: 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)