Tim Elhajj

Off the Microsoft stack!

Team Foundation 2012 Build Service installation and configuration


If you want to automate builds of your software projects, you can install Team Foundation Build Service from the Team Foundation Server product DVD and create a build machine. Once you have the build machine set up, you’ll want to create a build definition in Visual Studio with instructions about which code projects to compile and many other configurations. But first, you must set up the build machine.

Where to Install It?

The most important thing to concern yourself with during installation is selecting the right hardware to get the best performance (recommendations are linked below). If your team is building Windows apps, you’ll need to install the build service on Windows 8. See this topic on the Microsoft website: Build and Test a Windows Store App Using Team Foundation Build. All of the settings you choose during the initial configuration of Team Foundation Build Service can be changed after installation, so don’t worry too much about making a wrong choice. For a comprehensive explanation of Team Foundation Build Service architecture and all possible topologies, see this topic on the Microsoft website: Scale Out Your Build System.

Although you can install Team Foundation Build Service on the same computer as Team Foundation Server, you probably shouldn’t. You don’t want to hurt the performance of Team Foundation Server or increase its attack surface when builds are running.

System Requirements

The operating system requirements for Team Build match the requirements for TFS, and the hardware requirements match those of the operating system on which you install it. That said, you can optimize the performance of your build machine by installing Team Foundation Build Service on hardware adequate for the way your team intends to automate builds. See Hardware Recommendations on this MSDN topic.

Required permissions

You must be a member of both the Windows Administrators security group on the server on which you are configuring Team Foundation Build Service and the Project Collection Administrators group on TFS.

TIP: If you installed TFS, you’re already a member of Project Collection Administrators.

To run the Team Foundation Server installer

TIP: The build service is installed with TFS. If you want to set up the build service on the same server as where you installed TFS, you can skip this procedure, open the TFS Administration Console, select Build Configuration, and then choose Configure Installed Features.

1) Insert the Team Foundation Server DVD in the drive and launch the tfs_server.exe.

2) On the license terms dialog box, accept the license terms and then choose Install Now.

If you want to install Team Foundation Server to a specific location in the file system, choose the browse button (…) next to the default install location.

To configure Team Foundation Build Service

1) Choose Configure Team Foundation Build Service, and then choose Start Wizard. The Build Service Configuration wizard appears.

2) Read the Welcome screen, and then choose Next.

3) If you’re configuring the build service on the server running TFS, the default collection is selected automatically. Choose Next.

Otherwise, choose Browse, and then choose the team project collection to which you want this build controller to connect.

4) Choose Use the default setting, and specify the number of build agents. If you installed Team Foundation Build Service on the same server as Team Foundation Server, the default setting for Number of build agents to run on this build machine is 1 (recommended). Choose Next.

If you’re not installing build service on a server that’s running TFS or don’t want to use the default settings, perform one of the following steps:

* Choose Scale out build services to run concurrent builds across multiple machines. If you choose this option, you have to specify the number of build agents for this machine and then add them to a new or existing build controller. If you installed Team Foundation Build Service on its own server, the default setting for Number of build agents to run on this build machine is equal to the number of processor cores on this server.

* Choose Replace an existing build machine, and then specify the build machine to replace. This option copies the existing configuration to the new build server.

* Choose Configure later to skip setting up any build controllers or agents on this instance of Team Foundation Build Service. If you choose this option, you must manually connect the build controller to Team Foundation Server before you can use this build machine.

5) Under Run Team Foundation Build Service as, Choose Use a system account, and then choose NT Authority\Network Service. Choose Next.

Otherwise, choose Use a user account to use a domain or local account, and then enter the account name and password. To test the user account and password, choose Test.

6) Review the information and then choose Next.

The wizard validates your configuration. If you run into a problem, you can use the detailed results to identify the issue. If you can fix it, click the link to run the checks again.

7) Choose Configure. The wizard applies configuration settings.

8) At the success screen, choose Next.

9) Review the results of the success screen, including any recommendations. Choose Close

Author: Tim Elhajj

Tim is probably walking his dog.

8 thoughts on “Team Foundation 2012 Build Service installation and configuration

  1. Hello Tim,

    After installing TFS, I’m moving on to next steps of installing Build services.
    Tim, I need your expert guidance here as well.

    My model is 1 AT server, 1 DT server, 1 shared SharePoint server and 1 build server.
    Also, I am sure I would end up creating multiple Team Project Collections based on various organizational needs.
    Now the concern which bothers me is per MSDN link http://msdn.microsoft.com/library/dd793166.aspx

    My understanding after reading this through is that of constraints/limitations of having multiple Build Controllers on single build server.

    Looks like I need to buy extra Build servers for each TFS project collection I create because of the constraints/limitations.

    Is my assumption and understanding correct?
    Also, can you please guide in best possible way which is also supported by MS.

    Thanks for your help.

  2. You’re right on the money Sam. I think there is a hack you can use to get more than one build controller on a single server, but it’s not supported. On the other hand, you can use a single controller for multiple team projects in the same collection. Good luck!

  3. Thanks for the response. I think the un-supported clause would help me in convincing the Procurement team here.
    Starting the build process based on the steps mentioned in your e-book.Too good!

  4. Good deal, Sam! Good luck.

  5. Thanks for all the help and guidance Tim! Though it took me a mont, but I am glad I made it. Now after passing all issues, challenges and hurdles I have successfully migrated TFS2008 to TFS2012.
    Starting to work on ACL and security model integration.
    Thanks again!!

  6. Sam, my pleasure! Good luck.

  7. The builds service I was not able to configure. it is alwasys giving me Register Build service

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s