Configure and manage your build system

Do you want to automatically and consistently build, test, and deploy your app in a distributed environment? To get your team started using Team Foundation Build, you need one or more build servers in your build system.

What do you want to do?

• Deploy and work with a build server
  To use Team Foundation Build with an on-premises Team Foundation Server, you must deploy and dedicate at least one build server to your team project collection.

• Deploy and work with a build controller
  Use a build controller to perform lightweight tasks and distribute the processor-intensive work of your build process to its pool of build agents.

• Deploy and work with build agents
  Use build agents to do the processor-intensive work of your build, including provisioning the workspace, getting files from version control, compiling the code, and running tests.

• Set up drop folders
  Prepare and then designate one or more drop folders so that your build system can deliver binaries and log files to your team.

• Scale out your build system
  As your team and your code base grow, expand your build system incrementally with relative ease.

• Manage your build system
  Occasionally, you will need to monitor and manage your build system, confirm the health of your build server, or diagnose problems.

• Use your build system to compile, test, and deploy your app
  After your build system is in place, use it to automatically compile and test your applications, and perform other important functions.

• Receive build notifications
  Sign up for email alerts for yourself, and if you have sufficient permissions, for your team.

• Start, stop, delete, or destroy builds from the command prompt
  Use the command prompt directly or use a script. (We are not currently republishing this guidance. However, you can read the Visual Studio 2010 versions of the topics.)