A build agent is a computer capable of running a build. Each build agent possesses a number of predefined parameters that make it compatible for creating certain builds. Build agents are joined into a build grid.
To create a build, TeamCity tries to select the fastest agent based on the history of builds of a build configuration which ran on the particular agent. As the available build runners depend on environment where agent is running, TeamCity chooses an agent having required a build runner.
In TeamCity, a build agent can have following statuses:
| Status |
Description |
| Connected/ Disconnected |
An agent is connected if it is registered on the TeamCity server and responds to server commands, otherwise it is disconnected. This status is determined automatically. |
| Authorized/ Unauthorized |
Agents are manually authorized via the web UI. Only authorized build agents can run builds. The number of simultaneously authorized agents cannot exceed the number of agent licenses in your license pool. When an agent is unauthorized, a license is freed and a different build agent can be authorized. Purchase additional licenses to expand the number of agents that can concurrently run builds. When a new agent is registered on the server for the first time, it is unauthorized by default and requires manual authorization to run the builds.
 | If a build agent is installed and running on the same computer as TeamCity build server, it is authorized automatically. |
|
| Enabled/ Disabled |
Agents are manually enabled/disabled via the web UI. The TeamCity server only distributes builds to agents that are enabled.  | Agent disabling does not affect (stop) the build which is currently running on the agent. |
|
All agents connected to the server must have unique agent name.
Only users with certain roles can manage agents. See Role and Permission for more information.
For a build agent configuration please refer to Build Agent Configuration section.
See Also: