MSBuild

This page describes how to configure a Bamboo task to use an MSBuild executable.

To configure an MSBuild task:

1. Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
2. Click the name of the desired MSBuild task, or click Add Task and then MSBuild if creating a new task.

3. Complete the following settings:

   MSBuild configuration
   Task Description	A description of the task, which is displayed in Bamboo.
   Executable	The MSBuild executable that is available to perform the task. The executable that you select will become one of the task's (and so, the job's) requirements. You can add other executables, if required.
   Project File	The name of the solution, project file or MSBuild project to execute, e.g. ExampleSolution.sln. You can include variables (see Bamboo variables).
   Options	The MSBuild command line options that you want to include.  Bamboo tries to tokenise the contents of the Options field and passes those as arguments when it runs MSBuild. You should use a semi-colon to separate options, and quotes around parameters that contain spaces. For example: /p:Configuration="Any CPU";/p:PublishProfile="Dev Server" You can also include variables (see Bamboo variables).

4. If required, specify environment variables and working directory settings:

   Environment Variables	(Optional)  Additional system environment variables that you want to pass to your build. Note that existing environment variables are automatically available to the executable. You can also include Bamboo global or build-specific variables (see Bamboo variables). Multiple variables should be separated with spaces. Parameters with spaces must be quoted (e.g ANT_OPTS="-Xms200m -Xmx700m").
   Working Sub Directory	(Optional)  An alternative subdirectory, relative to the job's root directory, where Bamboo will run the executable. The root directory contains everything checked out from the job's configured source repository. If you leave this field blank, Bamboo will look for build files in the root directory. This option is useful if your task has a build script in a subdirectory and the executable needs to be run from within that subdirectory.
   Run as Powershell script	(Optional, Windows only) Check the 'Run as Powershell script' checkbox to run the script with Powershell instead of cmd.exe which interprets .bat files. The inline editor supports Powershell syntax.

5. Click Save.

Note that you cannot use Clover to collect code coverage for MSBuild builds, as Clover only supports builders of Java/Groovy-based projects, such as Ant, Maven or Grails.