Teamcity Agent For Mac


Hi Burhan, I believe you should try mounting your repo as a volume to your agent and server containers. You also can try using docker-compose to mount the volume. Once the volume is mounted, TeamCity should understand the absolute path inside the container where it is located. TeamCity Docker Support can run on Mac, Linux, and Windows build agents. It uses the docker executable on the build agent machine, so it should be runnable by the build agent user. On Linux, the integration will run if the installed Docker is detected. On Windows, the integration works for Linux and Windows container modes. The default agent pool is WIN but I wanted to run my tests on the MAC server. To change the agent pool to MAC, I tried to add Agent Requirement by setting to the MAC server from the list but it is not added to list of compatible agents associated with the project, but added to compatible agents with this warning on top of it. Sharma is somewhat correct, and KIR has it completely correct. I needed a build configuration for each server, Mac and Windows. Then I set a snapshot dependency from the Windows build on the Mac build (to make sure the Mac version builds completely first) and a artifact dependency from the same (to copy the resulting build output from the Mac to the Windows box). I've got TeamCity installed and working, and I need to have a build step run on a particular build agent (everything's running on Windows, but we have a Mac portion I need to build as well).

TeamCity provides the Docker Wrapper extension for Command Line, Maven, Ant, Gradle, .NET CLI (dotnet), and PowerShell runners. This extension allows running a build step inside the specified Docker image. Each of the supported runners has the dedicated Docker settings section.


The integration requires Docker installed on the build agents.

Supported Environments

Teamcity Agent For Mac Os

TeamCity Docker Support can run on Windows, Linux, and macOS build agents. It uses the docker executable on the build agent machine, so it should be runnable by the build agent user.

  • On Linux, the integration will run if the installed Docker is detected.

  • On Windows, the integration works for Linux and Windows container modes.

  • On macOS, the official Docker support for Mac should be installed for the user running the build agent.

Docker Settings

In the Docker Settings section of the build step settings, you can specify a Docker image which will be used to run the build step. Once an image is specified, all the following options become available.

Teamcity Agent Installer



Run step within Docker container

Specify a Docker image name as stated in the Docker Hub. TeamCity will start a container from the specified image and will try to run this build step within this container.

For example, ruby:2.4 will run the step within the Ruby container, version 2.4.

Docker image platform

Select <Any> (default), Linux, or Windows.

Pull image explicitly

If enabled, the image will be pulled from the Hub repository via docker pull <imageName> before the docker run command is launched.

Additional docker run arguments

Allows specifying additional options for docker run. The default argument is --rm, but you can provide more, for instance, add an additional volume mapping.

In this field, you cannot reference environment variables using %env.FOO_BAR% syntax because TeamCity does not pass environment variables from a build agent into a Docker container.

If you need to reference an environment variable on an agent, define the configuration parameter system.FOO_BAR=env_var_value in and reference it via %system.FOO_BAR%.

How It Works

Technically, the command of the build runner is wrapped in a shell script, and this script is executed inside a Docker container with the docker run command. All the details about the started process, text of the script, and so on, are written into the build log (the Verbose mode enables viewing them).

The checkout directory and most build agent directories are mapped inside the Docker process.

At the end of the build step with the Docker wrapper, a build agent runs the chown command to restore access of the buildAgent user to the checkout directory. This mitigates a possible problem when the files from a Docker container are created with the root ownership and cannot be removed by the build agent later.

If the process environment contains the TEAMCITY_DOCKER_NETWORK environment variable set by the previous Docker Compose build step, this network is passed to the started docker run command with the --network switch.

Environment Variables Handling

TeamCity passes environment variables from the build configuration into the Docker process, but it does not pass environment variables from the build agent, as they may not be relevant to the Docker container environment. The list of the passed environment variables can be seen in Verbose mode in the build log.

Skip to end of metadataGo to start of metadata

Teamcity Agent Macos

You are viewing documentation of TeamCity 7.x, which is not the most recently released version of TeamCity. Please refer to the listing to choose another version.

This page covers:

  • Installing Additional Build Agents

Before you can start customizing projects and creating build configurations, you need to configure build agents.

  • If you install TeamCity bundled with a Tomcat servlet container, or opt to install an agent for Windows, both the server and one build agent are installed. This is not a recommended setup for production purposes, since the build procedure can slow down the responsiveness of the web UI and overall TeamCity server functioning. If you need more build agents, perform the procedure described below.
  • For production installations it is recommended to adjust Agent's JVM parameters to include -server option.

Installing Additional Build Agents

Before the installation, please review Known Issues#Conflicting Software section.

Necessary OS and environment permissions

Please note that in order to run a TeamCity build agent, the user account under which the Agent is running should have the correct privileges, as described below.


  • Agent should be able to open HTTP connections to the server (to the same URL as server web UI)
  • Server should be able to open HTTP connections to the agent. The port is determined by 'ownPort' property of file (9090 by default) and the following hosts are tried:
    • host specified in the 'ownAddress' property of file (if any)
    • source host of the request received by the server when agent establishes connection to the server
    • address of the network interfaces on the agent machine

If the agent is behind NAT and cannot be accessed by any of addresses of agent machine network interfaces, please specify ownAddress in the agent config.


  • agent process (java) should be able to open outbound HTTP connections to the server address (the same address you use in the browser to view TeamCity UI) and accept inbound HTTP connections from the server to the port specified as 'ownPort' property in '<TeamCity agent home>/conf/' file (9090 by default). Please ensure that any firewalls installed on agent, server machine or in the network and network configuration comply with these requirements.
  • have full permissions (read/write/delete) to the following directories: <agent home> (necessary for automatic agent upgrade), <agent work>, and <agent temp>.
  • launch processes (to run builds).


  • Log on as a service (to run as Windows service)
  • Start/Stop service (to run as Windows service, necessary for agent upgrade to work, see also Microsoft KB article)
  • Debug programs (for take process dump functionality to work)
  • Reboot the machine (for agent reboot functionality to work)

For granting necessary permissions for unprivileged users, see Microsoft SubInACL utility. For example, to grant Start/Stop rights you might need to execute subinacl.exe /service browser /grant=<login name>=PTO command.


  • user should be able to run shutdown command (for agent machine reboot functionality and machine shutdown functionality when running in Amazon EC2)

Build-related Permissions
The build process is launched by TeamCity agent and thus shares the environment and is executed under the same OS user that TeamCity agent runs under. Please ensure that TeamCity agent is configured accordingly.
See Known Issues for related Windows Service Limitations.

Server-Agent Data Transfers


Please be sure to read through this section if you plan to deploy agent and server into non-secure network environments.

During TeamCity operations, both server establishes connections to the agents and agents establish connections to the server.

Please note that by default, these connections are not secured and thus are exposing possibly sensitive data to any third party that can listen to the traffic between the server and the agents. Moreover, since the agent and server can send 'commands' to each other an attacker that can send HTTP requests and capture responses can in theory trick agent into executing arbitrary command and perform other actions with a security impact.

It is recommended to deploy agents and the server into a secure environment and use plain HTTP for agents-to-server communications as this reduces transfer overhead.

It is possible to setup a server to be available via HTTPS protocol, so all the data traveling through the connections established from an agent to the server (incl. download of build's sources, artifacts of builds, build progress messages and build log) can be secured. See Using HTTPS to access TeamCity server for configuration details.

However, the data that is transferred via the connections established by the server to agents (build configuration settings, i.e., all the settings configured on the web UI including VCS root data) is passed via unsecured HTTP connection. For the time being TeamCity does not provide internal means to secure this data transfers (see/vote for TW-5815). If you want to secure the data you need to establish appropriate network security configurations like VPN connections between agent and server machines.

Installing Procedure

You can install build agent using any of the following installation options available:

After installation, please configure the agent specifying its name and address of TeamCity server in its conf/buildAgent.propertiesfile.
Then start the agent.

When the newly installed agent connects to the server for the first time, it appears on the Unauthorized agents tab under Agents, where administrators can authorize it. Please note that the tab is only visible for administrators/users with appropriate permission.


Agents will not run builds until they are authorized in the TeamCity web UI. The agent running on the same computer as the server is authorized by default.

If the agent does not seem to run correctly, please check the agent logs.

Installing via Java Web Start

  1. Make sure JDK 1.6+ is properly installed on the computer.
  2. On the agent computer, set up the JAVA_HOME environment variable to point to the JDK 1.6+ installation directory.
  3. Navigate to the Agents tab in the TeamCity web UI.
  4. Click the 'Install Build Agents' link and then click 'Via Java Web Start'.
  5. Follow the instructions.

    You can install the build agent Windows service during the installation process or manually.

Installing via a MS Windows installer

  1. Navigate to the Agents tab in the TeamCity web UI.
  2. Click the 'Install Build Agents' link and then click MS Windows Installer link to download the installer.
  3. Run the agentInstaller.exe Windows Installer and follow the installation instructions.

    Please ensure the user under whom the agent service is running has appropriate permissions

Installing via ZIP File

  1. In TeamCity Web UI, navigate to the Agents tab
  2. Click the Install Build Agents link and then click download zip file
  3. Unzip the downloaded file into the desired directory.
  4. Make sure that you have a JDK or JRE 1.6+ installed (You will need JDK (not JRE) for some build runners like IntelliJ IDEA, Java Inspections and Duplicates). Please ensure that the JRE_HOME or JAVA_HOME environment variables are set (pointing to the installed JRE or JDK directory respectively) for the shell in which the agent will be started.
  5. Navigate to the <installation path>conf directory, locate the file called and rename it to
  6. Edit the file to specify the TeamCity server URL and the name of the agent. Please refer to Build Agent Configuration section for more details on agent configuration
  7. Under Linux, you may need to give execution permissions to the bin/ shell script.

    On Windows you may also want to install the build agent windows service instead of manual agent startup.

Installing via Agent Push

TeamCity provide functionality that allows to install a build agent to a remote host. Currently supported combinations of server host platform and targets for build agents are:

  • from Unix based TeamCity server build agents can be installed to Unix hosts only(via SSH).
  • from Windows based TeamCity server build agents can be installed to Unix (via SSH) or Windows(via psexec) hosts.

SSH note
Make sure 'Password' or 'Public key' authentication is enabled on the target host according to preferred authentication method.

There are several requirements for the remote host that should be met:




Installed JDK(JRE) 1.6+ required. JVM should be reachable with JAVA_HOME(JRE_HOME) environment variables or be in paths. Also required 'unzip' utility and either 'wget' or 'curl'.


  • Installed JDK/JRE 1.6+ is required.
  • Sysinternals psexec.exe on TeamCity server required. It has to be accessible in paths. You can install it at AdministrationTools page.
    Note, that PsExec applies additional requirements to remote Windows host (for example, administrative share on remote host must be accessible). Read more about PsExec.

Installation Procedure

  1. In the TeamCity Server web UI navigate to AgentsAgent Push tab, and click Install Agent....

    Note, that if you are going to use same settings for several target hosts, you can create a preset with these settings, and use it next time when installing an agent to another remote host.

  2. In the Install agent dialog, if you don't yet have any presets saved, select 'Use custom settings', specify target host platform and configure corresponding settings.
  3. You may need to download Sysinternals psexec.exe, in which case you will see corresponding warning and a link to AdministrationTools page where you can download it.

You can use Agent Push presets in Amazon EC2 Cloud profile settings to automatically install build agent to started cloud instance.

Starting the Build Agent

To start the agent manually, run the following script:

  • for Windows:<installation path>binagent.bat start
  • for Linux and MacOS X:<installation path> start

    If you're running build agent on MacOS X and you're going to run Inspection builds, you may need to use the StartupItemContext utility:

To configure agent to be started automatically, see corresponding sections:
Mac OS X
Linux: configure daemon process with start command to start it and stop command to stop it.

Stopping the Build Agent

To stop the agent manually, run the <Agent home>agent script with a stop parameter.

Use stop to request stopping after current build finished.
Use stop force to request immediate stop (if a build is running on the agent, it will be stopped abruptly (canceled))
Under Linux, you have one more option top use: stop kill to kill the agent process.

If the agent runs with a console attached, you may also press Ctrl+C in the console to stop the agent (if a build is running it will be canceled).

Automatic Agent Start under Windows

To run agent automatically on machine boot under Windows you can either setup agent to be run as Windows service or use another way of automatic process start.
Using Windows service approach is the easiest way, but Windows applies some constraints to the processes run in this way.
TeamCity agent can work OK under Windows service (provided all the requirements are met), but is often not the case for the build processes that you will configure to be run on the agent.

That is why it is advised to run TeamCity agent as use Windows service only if all the build scripts support this.
Otherwise, it is adviced to use alternative ways to start TeamCity agent automatically.
One of the ways is to configure automatic user logon on Windows start and then configure TeamCity agent start (via agent.bat start) on user logon.

Build Agent as a Windows Service

In Windows, you may want to use the build agent Windows service to allow the build agent to run without any user logged on.
If you use Windows agent installer you have an option to install the service in the installation wizard.

Service system account


To run builds, the build agent should be started under a user with enough permissions for performing a build and managing the service. By default, Windows service in started under SYSTEM account. To change it, use the standard Windows Services applet (Control Panel Administrative Tools Services) and change the user for TeamCity Build Agent service.

The following instruction can be used to install the service manually. This procedure should also be performed to install second and following agents on the same machine as Windows services

To install the service:

  1. Make sure there is no TeamCity Build Agent Service <build number> service already installed, if installed, uninstall the agent.
  2. Check property in <agent home>launcherconfwrapper.conf file to contain valid path to Java executable in the JDK installation directory. You can use for agent installed with Windows distribution.
  3. Run the <agent home>/bin/service.install.bat file.

To start the service:

  • Run <agent home>/bin/service.start.bat
    (or use Windows standard Services applet)

To stop the service:

  • Run <agent home>/bin/service.stop.bat
    (or use Windows standard Services applet)

You can also use Windows net.exe utility to manage the service once it is installed.
For example (assuming the default service name):

The file <agent home>launcherconfwrapper.conf can also be used to alter agent JVM parameters.

User account that is used to run build agent service should have enough rights to start/stop agent service.


A method for assigning rights to manage services is to use the Subinacl.exe utility from the Windows 2000 Resource Kit. The syntax for this is:
SUBINACL /SERVICE MachineNameServiceName /GRANT=[DomainName]UserName[=Access]

Using LaunchDaemons Startup Files on MacOSx

For MacOSx, TeamCity provides ability to load a build agent automatically at the system startup using LaunchDaemons plist file.

To use LaunchDaemonsplistfile:

  1. Install build agent on Mac either via or via Java web-start
  2. Prepare conf/ file
  3. Fix launcher permissions, if needed: chmod +x buildAgent/launcher/bin/*
  4. Load build agent to LaunchDaemon via command:

    You have to wait several minutes for the build agent to auto-upgrade from the TeamCity server.

  5. To start the build agent on reboot, you have to copy buildAgent/bin/jetbrains.teamcity.BuildAgent.plist file to the /Library/LaunchDaemons directory. And if you don't want to run your agent as root (and you probably don't), you have to edit /Library/LaunchDaemons/jetbrains.teamcity.BuildAgent.plist file and add section like Also, make sure that all files under buildAgent directory are owned by your_user to ensure proper agent upgrade process.
  1. To stop build agent, run the following command:

If you need to configure TeamCity agent environment you can change <TeamCity Agent Home>/launcher/conf/wrapper.conf (JSW configuration). For example, to make the agent see Mono installed using MacPorts on Mac OS X agent you will need to add the following line:

Configuring Java

TeamCity Agent is a Java application and it requires JDK version 1.6 or later to work. Oracle JDK is recommended.
(Windows) .exe TeamCity distribution comes with appropriate Java bundled. If you run previous version of TeamCity agent you might need to repeat agent installation to update used Java.

Using x32 bit JDK is recommended. If you do not have Java builds, you may install JRE instead of JDK.
Using of x64 bit Java is possible, but you might need to double -Xmx and -XX:MaxPermSize memory values for the main agent process (see Configuring Build Agent Startup Properties and alike section for the server).

For .zip agent installation you need to install appropriate Java version (make it available via PATH) or available in one of the following places:

  • <Agent home>/jre
  • in the directory pointed to by JAVA_HOME or JRE_HOME environment variables.

You can download Java installation from Oracle, select Java SE, JDK, version 1.6, 32 bit.

Upgrading Java on Agents

If a build agent uses a Java version older than it is required by agent (Java 1.6 currently), you will see the corresponding warning at the agent's page. This may happen when upgrading to a newer TeamCity version, which doesn't support an old Java version anymore. To update Java on agents you can do one of the following:

  • If appropriate Java version is detected on the agent, the agent page provides an action to upgrade the Java automatically. Apon action invocation the agent will restart using another JVM installation.
  • (Windows) Since build agent .exe installation comes bundled with required Java, you can just reinstall the agent using .exe installer obtained from TeamCity server Agents page.
  • Install required Java on the agent and restart the agent - it should then detect it and provide an action to use newer Java in web UI.
  • Install required Java on the agent and configure agent to use it.

Installing Several Build Agents on the Same Machine

TeamCity treats equally all agents no matter if they are installed on the same or on different machines. However, before installing several TeamCity build agents on the same machine, please consider the following:

  • Builds running on such agents should not conflict by any resource (common disk directories, OS processes, OS temp directories).
  • Depending on the hardware and the builds you may experience degraded builds' performance. Ensure there are no disk, memory, or CPU bottlenecks when several builds are run at the same time.

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

  • The agents are installed in the separate directories.
  • The agents have distinctive workDir and tempDir directories in file.
  • Values for name and ownPort properties of are unique.
  • No builds running on the agents have absolute checkout directory specified.

Moreover, make sure you don't have build configurations with absolute checkout directory specified (alternatively, make sure such build configurations have 'clean checkout' option enabled and they cannot be run in parallel).

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

If you want to install additional agents as services under Windows, do not opt for service installation during installer wizard or install manually (see also a feature request), then
modify the <agent>launcherconfwrapper.conf file so that wrapper.console.title,, wrapper.ntservice.displayname and wrapper.ntservice.description properties have unique values within the computer. Then run <agent>binservice.install.bat script under user with sufficient privileges to register the new agent service.
See above for the service start/stop instructions.

See also:

Teamcity Agent For Mac
Page:Build Agent Configuration