Understanding Build Controller and Build Agent for TFS (Team Foundation Server)

In this post I will slightly explain the Build Controller and the Build Agent.

The following is step-by-step video for the post.

[youtube=http://youtu.be/K9s11aLPPgI]

 

Build Service is a Windows Service that can only has one Build Controller, configured for only one Team Project Collection and has multiple Build Agents as needed, of course there is a workaround to have multiple Build Controller on the same machine but this is not recommended in production environment, for more info see, Configuring Multiple TFS Build Controller on the Same Machine1-Build-Service-resources-3

Only one Build Controller can exist on the same machine, we can have Build Controller running with the TFS AT (Team Foundation Server Application Tier) but the Build Agent not recommended to be exist on the TFS AT, this because the Build Agent doing intensive work and we don’t want to slow down our TFS AT.2-Build-Controllers-and-Build-Agents-3

Example of Build Server that has one Build Controller, configured for one Project Collection and has multiple Build Agents.3-Build-Service-example-34-Build-Service-one-controller-multi-agents

Removing the build configuration so we can reconfigure and see the number of recommended Build Agents and the Windows Service.5-Remove-Build-configuation

If the Build is not configured we can see that there is no Windows Service.6-Build-Service-not-exist-before-configure-build-service-on-tfs

The Windows Service for the build exist if the build is configured (Registered).7-Build-Service-exist-after-configure-build-on-tfs

When the processor is (1) processor, the available Build Agent is (2) and the recommended is (1).

8-Number-of-build-agents-is-depend-on-number-of-processors-2

When the processor is (4) processor, the available Build Agent is (8) and the recommended is (1).

9-Number-of-build-agents-is-depend-on-number-of-processors-1

Links:

Scale out Your Build System 

Share This: