MSBuild Plugin

 

Plugin Information

Plugin ID msbuild
Latest Release 1.16
Latest Release Date Sep 17, 2012
Sources Github
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

This plugin allows you to use MSBuild to build .NET projects. To use this plugin, specify the location of MSBuild.exe on Hudson's configuration page.  It is usually situated in a subfolder of C:\WINDOWS\Microsoft.NET\Framework

Then, on your project configuration page, specify the name of the build file (.proj or .sln) and any command line
arguments you want to pass in. The files are compiled to the directory where Visual Studio would put them as well.

Labels:

plugin-builder plugin-builder Delete
tier3-compat-plugin tier3-compat-plugin Delete
tier3-hudson-plugin tier3-hudson-plugin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Oct 12, 2009

    Graeme English says:

    I have Hudson configured to use a slave node with .Net 3.5 for a job. That job r...

    I have Hudson configured to use a slave node with .Net 3.5 for a job. That job requires .Net 3.5 and I've configured the MSBuild path in the Master's configuration, however on executing the job it fails because it can't find MSBuild. The master only has .Net 2 but I'd have thought that the check should be made by the slave. Any way around this other than installing .Net 3.5 on the master?

  2. Mar 16, 2010

    Alexis Seigneurin says:

    Same issue as Graeme's one on my installation: the plugin checks the MSBuild pat...

    Same issue as Graeme's one on my installation: the plugin checks the MSBuild path on the master, not on the slave. I suppose this is a regression of version 1.2.

  3. Jul 07, 2010

    David Bacher says:

    If you're having issues with MSBuild paths on slaves, see issue #3632 for possib...

    If you're having issues with MSBuild paths on slaves, see issue #3632 for possible workarounds.

  4. Oct 10, 2010

    Aleksey Sergeev says:

    I have configured "MsBuild Build File" with path relative to Workspace folder "p...

    I have configured "MsBuild Build File" with path relative to Workspace folder "project\project.csproj". The real path is "C:\Program Files\.hudson\jobs\project\workspace\project\project.csproj" I receive "MSBUILD : error MSB1009: Project file does not exist." message during build. Build succeded if I set real path as "MsBuild Build File".

    Is it possible to set relative path to project as "MsBuild Build File?

    1. Jan 05, 2011

      Anthony Mayer says:

      I'm seeing the same problem. The best solution I've found is to run a windows ba...

      I'm seeing the same problem. The best solution I've found is to run a windows batch command that goes into the project directory and then run the msbuild task. You can also run a windows batch command to get the absolute path, run the job, and then use the absolute path for the msbuild task. I looked at the code it doesn't make sense that its doing this. Does anyone have a fix?

    2. Jun 23, 2011

      Michael Dopp says:

      simply use %WORKSPACE%\project\project.csproj

      simply use

      %WORKSPACE%\project\project.csproj

  5. Jan 28, 2011

    Serge Weinstock says:

    I have problems with parameterized builds. I would like to do an optional clean ...

    I have problems with parameterized builds. I would like to do an optional clean before the build. I've tried to define a parameter with the possible values "Build" or "Clean;Build". I was hoping to pass this value to the /target command line option. Unfortunately the parameters seem to be only passed as MSBuild parameters (i.e.: "/parameter:VAR_NAME=VAR_VALUE") and not as targets or environment variables which would be replaced by their values. Is there a way to get around this problem?