|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Working with Build Definitions in Team Foundation Build
This topic describes how to create and modify build definitions in Team Foundation Build.
Team Foundation Build uses build definitions to manage the conditions under which a single solution or a set of solutions will be built. You can use the Build Definition dialog box to create and modify build definitions. You have the following configuration options:
Use this setting to map the source control location of the files you want to build on the build agent. Each path is mapped to a relative location beneath a root build directory on the build agent.
Either use this setting to browse to an existing TFSBuild.proj file in source control or use it to create a new one to be associated with the build definition. If two or more build definitions share a TFSBuild.proj file, customizing it effects each build definition.
If you create a new TFSBuild.proj file you can specify which files to build, whether to run tests or code coverage, and which configuration or platform to build.
Use this setting to specify the retention policy for failed, stopped, partially-successful, or fully-successful builds.
Use this setting to specify the build agent, the computer on which the build runs, and the shared folder where the built files are stored.
Use this setting to specify:
Whether your build definition should run on demand
Whether your build definition should run continuously on each check-in
Whether each check-in should add a build to the queue to be run as soon as an agent is free