Jenkins: no tool named MSBuild found

Question

Setting up a Pipeline build in Jenkins (Jenkins 2.6), copying the sample script for a git-based build gives: "no tool named MSBuild found". I have set MSBuild Tool in Manage Jenkins -> Global Tool Configuration. I am running pipeline on the slave node.

In Slave configuration, I have set MSBuild tool path in Node Properties -> Tool Locations.
While build process it is not able to get MSBuild tool path, if i run same source without pipeline (without using Jenkinsfile) it works fine.

Please see Jenkinsfile Syntax

pipeline {
    agent { label 'win-slave-node' }
    stages {
           stage('build') {
           steps {

           bat "\"${tool 'MSBuild'}\" SimpleWindowsProject.sln /t:Rebuild /p:Configuration=Release"
           }
    }
   }
}

I have also tried to change environment variable for windows slave it not refreshed.

NOTE: I have installed MS Build tool for on slave node

Have you checked the console on which agent it was running while you are building. — Chandra Sekhar Y
Can you check this once "node('win-slave-node') { def MSBuild MSBuild= tool 'MSBuild' stage('Build') { bat(/"${MSBuild}" SimpleWindowsProject.sln /t:Rebuild /p:Configuration=Release/) } }" — Chandra Sekhar Y
Above is the same code with minor changes try once to check whether working/not — Chandra Sekhar Y
Can you check to make sure you called the tool MSBuild? You have it referenced one I'm above as "MBuild", without an S. — Kdawg
@Chandra Sekhar: Thanks for the code, but it is not working, the issue is not with code, it showing empty string on MSBuild variable. I have set vs2017 env variable by running vcvars64.bat in Jenkinsfile — Atul N

Nick Jones Nick Jones · Accepted Answer · 2017-08-09T13:56:42

In Declarative Pipeline syntax, the tooling for MSBuild is a little clunkier. Here's how I've had to handle it, using a script block:

pipeline {
  agent { 
    label 'win-slave-node'
  }
  stages {
    stage('Build') {
      steps {
        script {
          def msbuild = tool name: 'MSBuild', type: 'hudson.plugins.msbuild.MsBuildInstallation'
          bat "${msbuild} SimpleWindowsProject.sln"
        } 
      } 
    } 
  } 
}

In the older Scripted Pipeline syntax, it could be like this:

node('win-slave-node') {
  def msbuild = tool name: 'MSBuild', type: 'hudson.plugins.msbuild.MsBuildInstallation'

  stage('Checkout') {
    checkout scm
  }

  stage('Build') {
    bat "${msbuild} SimpleWindowsProject.sln"
  }
}

Jenkins: no tool named MSBuild found

5 Answers