Search

I had a look the screenshots about job configuration you post but are cutted (no one configuration is visible).

In the wiki page there are two pipeline example, anyway following the output of your pipeline job it's clear that you have an installation of NodeJS 6.10 in the system

[C:\Program Files (x86)\Jenkins\workspace\test-project-v0.1] Running shell script
+ node -v
v6.10.0

and it wins in the PATH variable, looks like the bin folder of the NodeJS of the system installation (6.10.0) is before the bin folder of Jenkins NodeJS installation.

When you execute the nom or node command it takes the system installation over the Jenkins installation and this is because you do not get grunt (because it was installed in Jenkins installation NodeJS).

• Verify the PATH variable in a shell command with the following command

  echo %PATH%

• Ensure you do not have the EnvInject plugin installed in Jenkins, otherwise you fall in JENKINS-26583 (as described in Known issues section of the wiki)
• In the pipeline try use

  nodejs(nodeJSInstallationName: 'node-4.6.0', configId: null) {
      bat 'bower -v'
  }
  

• As last chance uninstall the system NodeJS installation

As described in JENKINS-43593 you can also do the same suggested for the JDK/Maven

env.NODEJS_HOME = "${tool node-4.6.0}"
env.PATH="${env.NODEJS_HOME};${env.PATH}"
echo ${env.PATH}
bat 'node -version'

This will come over envinject plugin issue or any system installation

Thanks Nikolas.

• Yes you are right it is taking system installation. But I have installed in jenkins also. How can we change npm/node to get the path from Jenkins Installation.
• I checked EnvInject plugin is not installed in my Jenkins.
• I have also attached Jenkins Global Tool Configuration setting
• 

• Please see the attached snapshot for complete configuration of both the style.

How can we change npm/node to get the path from Jenkins Installation.

In my previous post there are two way to try

node {
   stage('build') {
      nodejs(nodeJSInstallationName: 'node-4.6.0', configId: null) {
          bat 'bower -v'
      }
   }
}

node {
   stage('build') {
      env.NODEJS_HOME = "${tool node-4.6.0}"
      env.PATH="${env.NODEJS_HOME};${env.PATH}"
      echo ${env.PATH}
      bat 'node -version'
   }
}

Thanks I tried first way & it solved the problem. But now i am getting another issue.
I have updated maven config in jenkins global setting. but I got this error

[C:\Program Files (x86)\Jenkins\workspace\lease-wallet-v0.1\Lease Wallet] Running shell script
+ mvnw clean
C:/Program Files (x86)/Jenkins/workspace/lease-wallet-v0.1/Lease Wallet@tmp/durable-7ca02bad/script.sh: line 2: mvnw: command not found
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // wrap
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 127
Finished: FAILURE

Please find attached snapshot for maven config. in Global setting.

Please Print your PATH variable

To have maven in your PATH do the same I posted above where instead of nodejs use

withMaven() \{
    bat 'mvn clean install'
}

https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin

Update wiki documentation on how use tool to contribute the PATH variable in the same manner the JDK on Maven tool suggest for pipeline.