CODEWITHSUNDEEP
c#.netmsbuildcontinuous-integrationjenkins
Bijoy K Jose
Bijoy K Jose

Reputation: 1372

build .net application in Jenkins using MSBuild

I have a .net application built on .net framework 3.5, I am trying to build this application on Jenkins CI server. I've added MSBuild plugin and and have added path to the .exe file of 2.0, 3.5 and 4.0 versions of MSBuild. But my building processes are failing by showing the below error message. 

Path To MSBuild.exe: msbuild.exe  
Executing command: cmd.exe /C msbuild.exe Neo.sln && exit %%ERRORLEVEL%%  
[Test project] $ cmd.exe /C msbuild.exe Neo.sln && exit %%ERRORLEVEL%%  
'msbuild.exe' is not recognized as an internal or external command,  
operable program or batch file.  
Build step 'Build a Visual Studio project or solution using MSBuild.' marked uild as failure  
Finished: FAILURE

Could anyone plz help me out..??

Upvotes: 38

Views: 79769

Answers (5)

Damith
Damith

Reputation: 63065

To make the MSBuild plugin work, you need to configure the plugin in the Jenkins management screen.

NOTE: in the newer Jenkins versions you find the MSBuild configuration in the Global Tool Configuration:

enter image description here

Jenkins MSBuild Installation Configuration

Note the "Name" field, where I've called this particular configuration v4.0.30319. You could call it anything you like, but ideally the name will somehow refer to the version.

You'll need to refer to this name later in the Jenkins PROJECT that's failing.

Note: The yellow warning implies that the Path to MSBuild field should be populated with a directory name rather than a file name. In practice you do need to enter the filename here too (ie. msbuild.exe) or the build step will fail.

In the Jenkins project that's failing, go to the MSBuild build step.

The first field in the build step is "MSBuild Version". If you created the build step before configuring any MSBuild versions, the value here will be (default).

Jenkins MSBuild build-step, with (default) msbuild configuration selected

After configuring one or more MSBuild versions, the drop down will be populated with the available configurations. Select the one you require.

You can see here that I've now selected the named configuration that matches the installation above.

Jenkins MSBuild build-step, with named msbuild configuration selected

Upvotes: 84

Ignacio Fernández
Ignacio Fernández

Reputation: 111

You can also add the path where the msbuild.exe is, to the PATH system environment variable of the node (or nodes) that is running that specific job.

Upvotes: 2

Pavel Zeman
Pavel Zeman

Reputation: 131

Jenkins | Manage Jenkins | Configure System

scroll down to the MSBuild section and click MSBuild installations

define the full path to msbuild.exe, on my system I have 3.5 and v4.0.30319

Note - specify the path to 32-bit tools even on a 64-bit system, otherwise you might get an error message:

Building Windows Phone application using MSBuild 64 bit is not supported.

So in Jenkins - it could be for example:

Name: Version 3.5

Path: C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe

Name: Version 4.0

Path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSbuild.exe

Upvotes: 13

Mel Padden
Mel Padden

Reputation: 1003

You could try executing the 

%comspec% /k ""c:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat"" x86

command, which will temporarily update your environment path variables to reflect the VS2010 build environment. Execute this before you call MSBUILD and see what happens. I use this in my own build scripts with no issues.

Side note; it's very likely counterproductive to have multiple versions of MSBUILD on your PATH. Concentrate on getting one version working and go from there.

Upvotes: -2

fmgp
fmgp

Reputation: 1636

I think you should set an absolute path for "msbuild.exe" in your Jenkins configuration, for example:

C:\Windows\Microsoft.NET\Framework\v3.5\msbuild.exe

Upvotes: 6

Related Questions