Configure Agent Installation
A build agent can be configured by adjusting in the
<TeamCity Agent Home>/conf/buildAgent.properties file.
General Agent Configuration
This Java properties configuration file can store properties that will be published on the server as agent properties and can participate in the Agent Requirements expressions. All system and environment properties defined in the file will be passed to every build run on the agent.
#in the first position of the line for a comment.
\as the path separator. If you need to include
\, escape it with another
Whitespaces are processed as any other symbol.
Example agent configuration file:
Make sure the file is writable for the build agent process itself. For example, that the file is updated to store its authorization token generated on the server-side.
name property is not specified, the server will generate a build agent name automatically. By default, this name will be created from the build agent's host name.
The file can be edited while the agent is running: the agent detects the change and (upon finishing a running build, if any) restarts automatically loading the new settings.
Build Agent Port
The port where the TeamCity build agent starts and where it listens for the incoming data from the server is determined via the
ownPort property (9090 by default). If the firewall is configured, make sure that the incoming connections for this port are allowed on the agent machine.
If more than one build agent is hosted on the same machine, different ports must be assigned to them via the
ownPort property in the
buildAgent.properties file of every agent.
Build Agent IP Address
When an agent connects to the TeamCity server for the first time, the agent automatically determines its IP address to use for connection, unless the
ownAddress property is defined. If the agent machine has several network interfaces, automatic detection may fail. In this case, it is recommended to specify the
Set up Agent Behind Proxy
It is possible to configure a forward proxy server for agent-to-server connections.
On the TeamCity agent side, specify the proxy to connect to the TeamCity server using the following properties in the
If the proxy has a HTTPS endpoint, you can also configure the
Note that the proxy has to be configured not to cache any TeamCity server responses. For example, if you use Squid, add "cache deny all" line to the