This page describes how to configure a Visual Studio (devenv.exe) executable for a Task. When creating a new Job or configuring an existing one, you need to specify the Tasks that will execute the Job's builds. You must specify an executable for each Task. If you specify an Ant, Grails or Maven executable, you will also need to choose a JDK. When creating a new Plan, you can configure the Tasks for the Plan's default Job. An executable is a program external to Bamboo used to automate processes. Generally, executables compile source code to generate compiled executable files (referred to as artifacts in Bamboo). Ant, Maven, MSBuild or PHPUnit are just some examples of executables that can be used as part of your build process.New executables can be defined as capabilities in Bamboo. Once an executable has been defined in Bamboo, it can be configured as part of a Task. |
On this page: |
Configuring a Visual Studio Executable for a Task
To configure a Visual Studio executable for a Task:
- Navigate to the Task configuration for the Job (this will be the default Job if creating a new Plan).
- Click the name of the desired Visual Studio Task, or click 'Add Task' and then 'Visual Studio' if creating a new Task.
- Update the Task settings:
- 'Task Description' — Enter a description of the Task, for display in Bamboo.
- 'Solution' — Enter the name of the Visual Studio solution file that you want Bamboo to execute each time the source code changes. For example:
run
. You can also include variables (see Using Global, Plan or Build-specific Variables). - 'Options' — Specify any Visual Studio command-line options that you want to include (e.g.
/build Debug
). You can also include variables (see Using Global, Plan or Build-specific Variables). - 'Platform' — Select the platform toolset required to compile your Solution. This is provided as an argument to
Vcvarsall.bat
(see this MSDN article for more details).
- If required, update the system environment variables and working directory settings:
- 'Environment Variables' (Optional) — Specify any additional* operating system environment variables you want to pass to your build; Please note, multiple variables must be separated with spaces, and parameters with spaces must be quoted (e.g 'ANT_OPTS=-Xms200m -Xmx700m'). You can also include Bamboo global or build-specific variables (see Using Global, Plan or Build-specific Variables).
* i.e. additional to the existing environment variables (see Viewing Bamboo's System Information for a list). Note that existing environment variables are automatically available to the executable, thus you don't need to specify them in the 'System Environment Variables' field. - 'Working Sub Directory' (Optional) — A subdirectory relative to the Job build's root directory where Bamboo will execute your specified executable's commands. The Job build's root directory contains everything checked out from your Job's configured source repository. If you leave this field blank, Bamboo will look for the build files in the build root directory (which is assumed to be the Working Directory, as described in Locating Important Directories and Files). 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, in which case, you would type the name of that subdirectory in this field.
- 'Environment Variables' (Optional) — Specify any additional* operating system environment variables you want to pass to your build; Please note, multiple variables must be separated with spaces, and parameters with spaces must be quoted (e.g 'ANT_OPTS=-Xms200m -Xmx700m'). You can also include Bamboo global or build-specific variables (see Using Global, Plan or Build-specific Variables).
- Click the 'Save' button to save your changes.
Notes
Related Topics
Attachments:


