The VCS Worker is an experimental feature currently not bundled with TeamCity.

VCS Worker

Interaction with version control (VCS) servers is one of the resource-heavy parts of TeamCity. Until TeamCity 8.0, VCS operations could only be performed by TeamCity server itself. In version 8.0, we introduced an option to execute VCS operations in a separate process (VCS Worker service), which can run on a separate machine; moreover, you can use several VCS Workers running on multiple machines to offload the server.

For example, you can route all Git VCS traffic through one VCS Worker and all Subversion traffic through another. Furthermore, you can run the TeamCity server on Linux and still be able to use TFS by running a VCS Worker on a Windows machine. With large installations, VCS Worker(s) installed on separate machines should noticeably decrease the TeamCity server load.

By default, VCS Workers are disabled and TeamCity behaves as usual, i.e. performs all VCS operations from the main server process.

A VCS Worker supports Team Foundation Server, Perforce, Subversion, Git, and Mercurial.

Installing VCS Worker

Before installing, make sure that the TeamCity server and the VCS Worker versions are the same. Unlike TeamCity build agents, VCS Worker currently does not support auto-upgrade, this means you need to upgrade it manually each time when you install new version of TeamCity.

Configuring Worker

You can modify a number of settings for your VCS Worker: check <vcs-worker>/conf/ for all available options.

Running Several VCS Workers

TeamCity uses round-robin selection of VCS Workers if there are several VCS Workers available to serve an operation. Additional filters can be configured: see the <vcs-worker>/conf/ file for all available options.

Binary package

VCS worker plugins for different versions of TeamCity: