

If the agent is behind NAT and cannot be accessed by any of addresses of the agent machine network interfaces, please specify the ownAddress property in the Build Agent Configuration file. The addresses of the network interfaces on the agent machine

If a proxying server is used, it must be correctly configured. The source IP of the HTTP request received by the server when the agent establishes a connection to the server. The address specified in the ownAddress property of the Build Agent Configuration file (if any)

The agent port is determined using the ownPort property of the Build Agent Configuration file as the starting port (9090 by default, next port is used if the specified port is busy), and the following IP addresses are tried: Since TeamCity 10, by default unidirectional agent-to-server connection via polling protocol is used by TeamCity.įor the fallback bidirectional communication, in addition for the agent to server connections, the server must be able to open HTTP connections to the agent. Please note that in order to run a TeamCity build agent, the user account used to run the Agent requires the following privileges:Īn agent must be able to open connections to the server using the server address specified in the serverUrl property (usually the same URL as the server web UI). In case of any issues, make sure no conflicting software is used. If you need the agent to run a operating system different from the TeamCity server, perform the procedure described below.įor production installations, it is recommended to adjust the Agent's JVM parameters to include the -server option.īefore the installation, please review the Conflicting Software section. If you need more build agents, perform the procedure described below. This is not a recommended setup for production purposes because of security concerns and since the build procedure can slow down the responsiveness of the web UI and overall TeamCity server functioning. If you install TeamCity bundled with a Tomcat servlet container, or use the TeamCity installer for Windows, both the server and one build agent are installed on the same machine. Please review the agent-server communication and Prerequisitessection before proceeding with agent installation.

Setting up and Running Additional Build Agentsīefore you can start customizing projects and creating build configurations, you need to configure build agents.
