This documentation is archived and is not being maintained.

How to: Queue or Start a Build Definition

You can use build definitions in Team Foundation Build to define the settings under which a team project is built. Before you queue a build, you must first create a build definition. For more information, see How to: Create a Build Definition.

Required Permissions

To perform this procedure, you must have the Team Foundation Server Start a build permission set to Allow. For more information, see Team Foundation Server Permissions.

All files for a build are downloaded to the build computer (build directory) folder. If you accepted the default settings when you created the build definition, these files are located in the TeamBuildTypes folder in Team Foundation version control.


Build definitions for Microsoft Office solutions are not supported and are likely to build incorrectly. For more information, see the Microsoft Knowledge Base article, INFO: Considerations for Server-Side Automation of Office (;en-us;257757).

To queue a build using a build definition

  1. In Team Explorer, select the appropriate team project.

  2. On the Build menu, click Queue New Build to display the Queue Build {Team Project Name} dialog box.

  3. From the Build definition drop-down list, select a build definition.

    If the build definition you selected has a description, the description appears in the text box directly under the Build definition drop-down list.

  4. Select a build agent from the Build agent drop-down list.

    By default, the build agent that is associated with the build definition you chose is displayed.

  5. The Drop folder for this build text box displays the folder where the built files and binaries will be stored as soon as the build is completed.

  6. Select a priority for your build from the Priority in queue drop-down list.

    You can select from High, Above Normal, Normal, Below Normal and Low. By default, Normal is displayed.

    The Position text box displays the estimated position in queue based on agent and priority.

  7. In the MSBuild command-line arguments (optional) text box, you can enter optional MSBuild arguments. For example

    /v:diag /p:versionToGet="myVersion"

    These arguments are specific to the build you are queuing. If you want to pass command-line arguments to all builds for a given build definition, you must use the response file (.rsp) for that build definition. For more information about MSBuild command-line arguments, see MSBuild Command Line Reference. For more information about response files, see MSBuild Response Files.

  8. Click Queue to enter the build in the build queue.

    The Queued tab of the Builds Explorer appears. For more information, see Understanding the Team Foundation Build Explorer.