Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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..??

like image 612
Bijoy K Jose Avatar asked Apr 19 '12 12:04

Bijoy K Jose


People also ask

Can Jenkins be used for .NET applications?

NET build system in Jenkins workflow to build your . NET apps, as soon as there are changes in the repository.

Does Jenkins use MSBuild?

Usage. To use this plugin, specify the location directory of MSBuild.exe on Jenkin's configuration page. The MSBuild executable is usually situated in a subfolder of C:\WINDOWS\Microsoft.NET\Framework.


1 Answers

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

like image 175
Damith Avatar answered Sep 28 '22 11:09

Damith