Install Multiple Agents on One Machine

If a machine is capable of running several concurrent builds, you can install multiple TeamCity agents on it. However, we recommend running a single agent per (virtual) machine to minimize builds cross-influence and make builds more predictable.

TeamCity treats all agents equally regardless of whether they are installed on the same or on different machines.

When installing multiple TeamCity build agents on the same machine, consider the following:

• The builds running on such agents should not conflict for any resource (common disk directories, OS processes, OS temp directories).

• Depending on the hardware and the builds' specifics, you may experience degraded building performance. Ensure there are no disk, memory, or CPU bottlenecks when several builds are running at the same time.

After having one agent installed, you can install additional agents by following the regular installation procedure (see an exception for the Windows service below), but make sure that:

• The agents are installed using different OS users so that user-level resources (like Maven/Gradle/NuGet local artifact caches) do not conflict.

• The agents are installed in separate directories.

• The agents have the distinctive workDir and tempDir directories in the buildAgent.properties file.

• Values for the name and ownPort properties of buildAgent.properties are unique.

• No build configurations specify the absolute path to the checkout directory (or, if necessary, you can enable the "clean checkout" option and make sure they do not run in parallel).

Usually, for a new agent installation, you can just copy the directory of an existing agent to a new place except its temp, work, logs, and system directories. Then, modify conf/buildAgent.properties with the new name and ownPort values. Clear (delete or remove the value) the authorizationToken property and make sure the workDir and tempDir are relative / do not clash with another agent.