Queuing a Build for Team Foundation Server 2010 (Team Explorer Everywhere)
To run a build, you queue a build definition. By doing this, you add that build configuration to the queue of builds to be run by a specific build agent. The order in which builds are run depends on the build priority and the order in which the build requests were queued. Each build definition specifies whether the build should run manually or be triggered automatically. However, regardless of how a build is defined, you can manually queue any build whenever you want the build system to run it.
Required Permissions
To perform this procedure, your Queue builds permission must be set to Allow. For more information, see the following page on the Microsoft Web site: Team Foundation Server Permissions.
To queue a build for Team Foundation Server 2010
In Team Explorer, expand the team project for which you want to queue a build.
Expand the Builds node, right-click the build definition that you want to queue, and click Queue New Build.
The Queue Build dialog box appears.
In Build definition, verify that the specified definition is the one that you want to queue.
If the build definition you selected has a description, it appears in the box directly under the Build definition list.
In Build agent, specify the build agent that you want to perform the build.
By default, the build agent appears that is associated with the build definition that you specified.
In Drop folder for this build, verify that the path is the one to which you want the build output to be copied.
By default, the drop folder value is the one that was specified in the build definition. You must provide a valid path to a Windows file share (or a Server Message Block share). You must specify the path in the Uniform Naming Convention (UNC) format, such as \\ServerName\Share.
In Priority in queue, specify a priority for your build.
The Position box displays the estimated position in the build queue based on agent and priority.
In MSBuild command-line arguments (optional), you can enter optional MSBuild arguments.
For example, you might specify the following parameters:
/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 or response files, see the following pages on the Microsoft Web site: MSBuild Command Line Reference and MSBuild Response Files.
Click Queue to enter the build in the build queue.
The Queued tab of Build Explorer appears. For more information, see Using Build Explorer to View and Manage Queued, Ongoing, and Completed Builds.
See Also
Tasks
Creating a Build Definition for Team Foundation Server 2010
Modifying a Build Definition for Team Foundation Server 2010
Queuing a Build for Team System 2008 Team Foundation Server
Queuing a Build for Visual Studio 2005 Team Foundation Server