Deploying and configuring a build agent for TFS-MTM integration

With Team Foundation Build (TFBuild), you can create and manage build processes that automatically compile and test your applications, and perform other important functions. You can use your build system to support a strategy of continuous integration or put even more rigorous quality checks in place that prevent bad quality code from breaking the build.

When you specify the working directory, which the build agent uses to read from or write to files, please ensure the path to the working directory is not too long. Specifically, the specified working directory must not cause the build agent to produce any physical paths that are longer than 259 characters (learn more). Otherwise, your builds might fail and log this error: TF10128: The path <PhysicalPath> contains more than the allowed 259 characters. Type or select a shorter path. When you encounter this issue, names of TestArchitect test results which are uploaded to TFS are shortened (learn more).

Deploying build agent - XAML builds
To use TFBuild, you must have at least one build agent. A build agent does the processor-intensive work of your build, which includes getting files from version control, provisioning the workspace, compiling the code, running tests, and merging files back into version control. Each build agent is dedicated to a single build controller.

Deploying a Windows build agent - TFBuild
For TFBuild build definitions, to build Visual Studio solutions, you’ll need at least one Windows build agent.