[JIRA] (JENKINS-53347) NPM cannot find node binary
Title: Message Title Jon Rimmer updated JENKINS-53347 Jenkins / JENKINS-53347 NPM cannot find node binary Change By: Jon Rimmer Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53347) NPM cannot find node binary
Title: Message Title Jon Rimmer updated JENKINS-53347 OK, I figured this out: The jenkins/blueocean image is based on Alpine Linux, but the binaries downloaded by the nodejs plugin are not compatible with it. Jenkins / JENKINS-53347 NPM cannot find node binary Change By: Jon Rimmer Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53347) NPM cannot find node binary
Title: Message Title
Jon Rimmer updated an issue
Jenkins / JENKINS-53347
NPM cannot find node binary
Change By:
Jon Rimmer
1. Create a new Jenkins environment: {code:java}docker run --name jenkins -u root --rm -d -p 8080:8080 -v jenkins-data:/var/jenkins_home jenkinsci/blueocean:latest{code}2. Add node-8.11.3 as a global tool named "node".3. Add the following pipeline:{code:java}pipeline {agent anytools {nodejs 'node'}stages {stage('Example') {steps {sh 'npm --version'}} }}{code} 4. Run it.The result:{code:java}Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/test[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Tool Install)[Pipeline] tool Unpacking https://nodejs.org/dist/v8.11.3/node-v8.11.3-linux-x64.tar.gz to /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node on Jenkins [Pipeline] envVarsForTool[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline] { ( ‘ Example ’ )[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] sh[test] Running shell script+ npm --versionenv: ‘node’: No such file or directory[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 127Finished: FAILURE{code}I see in the past this has happened due to an issue with the "env-inject" plugin, but that issue has been fixed, and I do not have that plugin installed.
Add Comment
[JIRA] (JENKINS-53347) NPM cannot find node binary
Title: Message Title
Jon Rimmer updated an issue
Jenkins / JENKINS-53347
NPM cannot find node binary
Change By:
Jon Rimmer
1. Create a new Jenkins environment: {code:java}docker run --name jenkins -u root --rm -d -p 8080:8080 -v jenkins-data:/var/jenkins_home jenkinsci/blueocean:latest{code}2. Add node-8.11.3 as a global tool named "node".3. Add the following pipeline:{code :java }pipeline {agent anytools {nodejs 'node'}stages {stage( ‘ ' Example ’ ' ) {steps {sh 'npm --version'}} }}{code} 4. Run it.The result:{code:java}Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/test[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Tool Install)[Pipeline] toolUnpacking https://nodejs.org/dist/v8.11.3/node-v8.11.3-linux-x64.tar.gz to /var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node on Jenkins[Pipeline] envVarsForTool[Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline] { (‘Example’)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] sh[test] Running shell script+ npm --versionenv: ‘node’: No such file or directory[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 127Finished: FAILURE{code}I see in the past this has happened due to an issue with the "env-inject" plugin, but that issue has been fixed, and I do not have that plugin installed.
Add Comment
[JIRA] (JENKINS-53347) NPM cannot find node binary
Title: Message Title
Jon Rimmer created an issue
Jenkins / JENKINS-53347
NPM cannot find node binary
Issue Type:
Bug
Assignee:
Nikolas Falco
Components:
nodejs-plugin
Created:
2018-08-30 10:44
Environment:
jenkinsci/blueocean:1.8.2 jenkins:2.121.3 org.jenkins-ci.plugins:nodejs:1.2.6
Priority:
Major
Reporter:
Jon Rimmer
1. Create a new Jenkins environment:
docker run --name jenkins -u root --rm -d -p 8080:8080 -v jenkins-data:/var/jenkins_home jenkinsci/blueocean:latest
2. Add node-8.11.3 as a global tool named "node". 3. Add the following pipeline:
pipeline {
agent any
tools {
nodejs 'node'
}
stages {
stage(‘Example’) {
steps {
sh 'npm --version'
}
}
}
}
4. Run it. The result:
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/test
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Tool Install)
[Pipeline] tool
Unpacking
