What's new in Team Foundation Build

When you install or upgrade to Visual Studio Team Foundation Server 2013, you and your team can benefit from new features.

Define a build process

You can build code in a Git team project. See Create or edit a build definition.
Defining a build is simpler. See Use the Default Template for your build process.
Building and testing a Windows Store app is simpler. See Build and test a Windows Store app using Team Foundation Build.
You have a new option organize build output files into the same folder structure that is used by Visual Studio on your dev machine. See Default Template: Specify the build output location
The Logging Verbosity parameter is no longer required. Verbose data about each build is recorded in the diagnostic logs.
You can use only the Visual Studio Test Runner to run your tests. The MSTest option is no longer available.

You can run batch and PowerShell scripts before and after compilation, and before and after your tests run. See Run and pass data to scripts and programs
The default templates have a simpler and less granular structure to make them easier to customize.
The default templates are stored in an immutable location on your Team Foundation Server instead of in version control. You can download a copy, customize it, and then check in (TFVC) or commit and push it (Git) into your team project. See Customize your build process template.
You can use environment variables in your build process. See Team Foundation Build environment variables.
We’ve enhanced our guidance. See Customize your build process.

You can undock the Builds page from Team Explorer and open it in a new window.

You can view a diagnostic log for every build, regardless of whether or not you drop your build outputs. See Diagnose problems in your build.

You can drop your build outputs into TFS from both Visual Studio Online and on-premises servers.