Configuration settings of the build agent are stored in the
<TeamCity Agent Home>/conf/buildagent.properties file.
The file can also store properties that will be published on the server as Agent properties and can participate in the Agent Requirements expressions.
All the system and environment properties defined in the file will be passed to every build run on the agent.
The file is a Java properties file.
A quick guide is:
- use "
#" in the first position of the line for a comment
- use "
/" instead of "\" as the path separator. If you need to include "\" escape it with another "\".
- whitespaces within a line matter
This is an example of the file:
If the "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.
If the default polling protocol is changed in favor of legacy bidirectional communication between the server and the agent, the server must be able to open HTTP connections to the agent.
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 computer.
The IP address used by TeamCity server to connect to the build agent is automatically detected by the server when the agent first connects to TeamCity, unless the ownAddress property is defined. If the machine has several network interfaces, automatic detection may fail and it is recommended to specify the
Set up Agent behind Proxy
Since TeamCity 2017.1 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 TeamCity server using the following properties in the
Note that the proxy has to be configured not to cache any TeamCity server responses; e.g. if you use Squid, add "cache deny all" line to the