Skip to end of metadata
Go to start of metadata
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.

Table of Contents

This page covers new TeamCity server installation. For upgrade instructions, please refer to Upgrade.

The installation procedure consists of:

This page covers:

Installing the TeamCity Server

After you obtained the TeamCity installation package, proceed with corresponding installation instructions:

  • Windows .exe distribution - executable which provides installation wizard for Windows platforms and allows to install server as a Windows service;
  • .tar.gz distribution - archive with "portable" version suitable for all platforms;
  • .war distribution - for experienced users that want to run TeamCity in separately installed Web application server.

After installation, TeamCity web UI can be accessed via web browser. Default addresses are http://localhost/ for Windows distribution and http://localhost:8111/ for tar.gz distribution.

If you cannot access TeamCity web UI after successful installation, please refer to #Troubleshooting TeamCity Installation Issues section.

(info) The build server and one build agent will be installed by default for Windows, Linux or MacOS X. If you need more build agents, refer to the section Installing Additional Build Agents.

(warning) By default, TeamCity uses an HSQLDB database that does not require special configuring. This database works fine for testing and evaluating the system.
For production purposes using a standalone external database is recommended.

Installing TeamCity via Windows installation package

For the Windows platform, run the executable file and follow the installation instructions. You have options to install the TeamCity web server and one build agent that can be run as a Windows service.

If you opted to install the services, use standard Windows Services applet to manage the service.
Otherwise, use standard scripts.

If you did not change the default port (80) during the installation, the TeamCity web UI can be accessed via "http://localhost/" address in a web browser running on the same machine as the server is installed on. Please note that 80 port can be used by other programs (e.g. Skype, or other web servers like IIS). In this case you can specify another port during the installation and use "http://localhost:<port>/" address in the browser.

(info) If you want to edit the TeamCity server's service parameters, memory settings or system properties after the installation, please refer to the Configuring TeamCity Server Startup Properties section.

Service account


Please make sure the user account specified for the service has:

  • write permissions for the TeamCity Data Directory,
  • write permissions for the TeamCity Home directory, i.e. directory where TeamCity was installed,
  • all the necessary permissions to work with the source controls used. This includes:
    • access to Microsoft Visual SourceSafe database (if Visual SourceSafe integration is used).
    • the user, under which TeamCity server service runs, and ClearCase view owner are the same (if ClearCase integration is used).

By default, Windows service is installed under SYSTEM account. To change it, use the Services applet (Control Panel | Administrative Tools | Services)

Installing TeamCity bundled with Tomcat servlet container (Linux, Mac OS X, Windows)

Please review software requirements before the installation.

Unpack TeamCity<version number>.tar.gz archive (for example, using tar xfz TeamCity<version number>.tar.gz command under Linux, or WinZip, WinRar or alike utility under Windows).
Please use GNU tar to unpack. (for example, Solaris 10 tar is reported to truncate too long file names and may cause a ClassNotFoundException when using the server after such unpacking. Consider getting GNU tar at Solaris packages or using gtar xfz command)

Ensure you have JRE or JDK installed and JAVA_HOME environment variable is pointing to the Java installation directory. Latest Oracle Java 1.6 update is recommended.

Starting TeamCity server

If TeamCity server is installed as Windows service, follow the usual procedure of starting and stopping services.

If TeamCity is installed into existing web server (.war distribution) please start the server according to it's documentation. Please make sure to configure TeamCity-specific logging-related properties

If TeamCity is installed using .exe or .tar.gz distributions, TeamCity server can be started and stopped by the scripts provided in the <TeamCity home>/bin directory.

To start/stop TeamCity server and one default agent at the same time, use the runAll script.

To start/stop only the TeamCity server, use teamcity-server script and pass the required parameters. Start the script without parameters to see usage instructions.

For example:

  • Use runAll.bat start to start the server and the default agent
  • Use runAll.bat stop to stop the server and the default agent

By default, TeamCity runs on http://localhost:8111/ and has one registered build agent that runs on the same computer.

See below for changing the server port.

If you need to pass special properties to the server, please refer to Configuring TeamCity Server Startup Properties.

Headless mode for TeamCity


If you are running TeamCity on a server that is not running a windowing system, for example, console mode under Linux, then you may encounter this error when hitting the Statistics page:

javax.el.ELException: Error reading 'graphInfo' on type jetbrains.buildServer.serverSide.statistics.graph.BuildGraphBean

You can resolve this problem by adding -Djava.awt.headless=true server JVM option.

Installing TeamCity into Existing J2EE Container

  1. Copy the downloaded TeamCity<version number>.war file into the web applications directory of your J2EE container under teamCity.war name or deploy the .war following documentation of the web server. Please make sure there is no other version of TeamCity deployed (e.g. do not preserve old TeamCity web application directory under web server applications directory).
  2. Configure TeamCity logging properties by specifying log4j.configuration and teamcity_logs internal properties when starting the web server. Up-to-date values can be looked up in the bin/teamcity-server script available in .exe and tar.gz distributions. Recommended conf/teamcity-server-log4j.xml file content can be also found in .exe and tar.gz distributions. The one with debug enabled can be also found under TeamCity Data Directory\config_logging\debug-general.xml name after server's first start. See also sample teamcity-server-log4j.xml file.
  3. Ensure TeamCity web application is devoted sufficient amount of memory. Please increase the sizes accordingly if you have other web applications running in the same JVM.
  4. If you are deploying TeamCity to Tomcat container, please add useBodyEncodingForURI="true" attribute to the Connector tag for the server in Tomcat/conf/server.xml file.
  5. If you are deploying TeamCity to Jetty container version >7.5.5 (including 8.x.x) please make sure system property org.apache.jasper.compiler.disablejsr199 is set to true
  6. Ensure servlet container is configured to unpack deployed war files. Though for most servlet containers it is the default behaviour, for some it is not (e.g. Jetty version >7.0.2) and must be explicitly configured. TeamCity can not start while packed and will prompt about this in logs and UI.
  7. Configure appropriate TeamCity Data Directory to be used by TeamCity.
  8. Restart the server or deploy the application via servlet container administration interface and access http://server/TeamCity-NNN/, where "TeamCity-NNN" is the name of the war file. You might also need to rename the file to exclude build number from the name.

TeamCity J2EE container distribution is tested to work with Tomcat 7 servlet container. (See also Supported Platforms and Environments#The TeamCity Server)


If you're using Tomcat J2EE container, make sure Apache Portable Runtime feature of this container is disabled (actually it is disabled by default). Unfortunately because of bugs in Apache Portable Runtime TeamCity may not work properly in this case.

Autostart TeamCity server on Mac OS X

Starting up TeamCity server on a Mac is quite similar to starting Tomcat on Mac.

  • Install TeamCity and make sure it works if started from command line, with bin/ start. We'll assume that TeamCity is installed in /Library/TeamCity folder
  • Create file /Library/LaunchDaemons/jetbrains.teamcity.server.plist with the following content:
  • Test your file by running launchctl load /Library/LaunchDaemons/jetbrains.teamcity.server.plist . This command should start TeamCity server (you can see this from logs/teamcity-server.log and in browser)
  • If you don't want TeamCity to start under root permissions, specify UserName key in the plist file, like this:
  • That's it. TeamCity now should autostart when machine starts.

Using another Version of Tomcat

If you want to use another version of Tomcat web server instead of bundled one, you have the choices of whether to use .war TeamCity distribution or do Tomcat upgrade/patch for TeamCity installed from .exe or .tar.gz distributions.
For the latter, you might want to:

  • backup current TeamCity home
  • delete/move out the directories from TeamCity home which are also present in Tomcat distribution
  • unpack Tomcat distribution into TeamCity home directory
  • copy TeamCity-specific files from the previously backed-up/moved directories to the TeamCity home. Namely:
    • files under bin which are not present in the Tomcat distribution
    • delete default Tomcat conf directory and replace it with TeamCity-provided one
    • delete default Tomcat webapps/ROOT directory and replace it with TeamCity-provided one

Installation Configuration

Troubleshooting TeamCity Installation

Upon successful installation, TeamCity server web UI can be accessed via a web browser.
The default address that can be used to access TeamCity from the same machine depends on the installation package and installation options. (Port 80 is used for Windows installation, unless another port is specified, port 8111 for .tar.gz installation unless not changed in the server configuration).

If TeamCity web UI cannot be accessed, please check:

  • the "TeamCity Server" service is running (if you installed TeamCity as a Windows service);
  • TeamCity server process (Tomcat) is running (it is java process run in <TeamCity home>/bin directory);
  • if you run the server from a console, check console output;
  • check teamcity-server.log and other files in the <TeamCity home>\logs directory for error messages.

One of the most common issues with the server installation is using a port that is already used by another program. See
more on changing the default port.

Changing Server Port

If you use TeamCity server Windows installer you can set the port to use during installation.
If you use .war distribution please refer to the manual of the application server used.

Use the following instructions to change the port if you use .tar.gz distribution
If another application uses the same port that TeamCity server, TeamCity server (Tomcat server) won't start and this will be identified by "Address already in use" errors in the server logs or server console.

To change the server's port, in the <TeamCity Home>/conf/server.xml file, change the port number in the HTTP/1.1 connector (here the port number is 8111):

To apply changes, you should restart the server.

If you run another Tomcat server on the same machine, you might need to also change other Tomcat server service ports (search for "port=" in the server.xml file).

If you want to use https:// protocol, it should be enabled separately and the process is not specific to TeamCity, but rather for the web server used (Tomcat by default). See also Using HTTPS to access TeamCity server

Java Installation

TeamCity server is a web application that runs in an J2EE application server (a JVM application). A JVM application requires a JRE installation to run.

TeamCity (both server and agent) requires JRE 1.6 (or later) to operate. Using latest Oracle JSDK 1.6 is recommended (download page). Please also note that TeamCity agent needs JDK (not JRE) to operate properly.

The necessary steps to prepare Java installation depends on the distribution used.

  • Windows Installer (.exe) has JRE bundled (in jre directory). If you need to update the JRE used by the installation:
    • if you run the server from console refer to instructions for .tar.gz distribution below.
    • if you run as Windows service and want to upgrade JRE to newer 32 bit version, you can replace <TeamCity home>\jre with JRE from the newer installation (just install JRE per installation instructions and copy the content of the resulting directory to replace the content of the existing "jre" directory).
    • if you run as Windows service and want to upgrade JRE to 64 bit version, you will need to replace <TeamCity home>\jre with appropriate JRE. That's all for TeamCity 7.1+. If you use TeamCity 7.0 also replace/update bundled Tomcat Windows binaries: copy/overwrite content of bin\x64 directory to bin.
  • .war distribution depends on the application server used. Please refer to the manual of the server.
  • To use .tar.gz distribution and teamcity-server or runAll scripts you need to have JRE installed either in <TeamCity home>\jre or into another location. If another location is used, ensure there is no <TeamCity home>\jre directory present and one of the environment variables is defined: JRE_HOME (pointing to home directory of installed JRE), or JAVA_HOME (pointing to home directory of installed JSDK).

Setting Up Memory settings for TeamCity Server

As a JVM application, TeamCity only utilizes memory devoted to the JVM. Memory used by JVM usually constitutes of: heap (configured via -Xmx), permgen (configured via -XX:MaxPermSize), internal JVM (usually tens of Mb), OS-dependent memory features like memory-mapped files. TeamCity mostly depends on heap and permgen memory and these settings can be configured for the TeamCity application manually by passing -Xmx (heap space) and -XX:MaxPermSize (PermGen space) options to the JVM running the TeamCity server.

  • For initial use of TeamCity for production purposes (assuming 32 bit JVM) minimum recommended settings are: -Xmx750m -XX:MaxPermSize=270m. If slowness or OutOfMemory error occurs, please increase the settings to -Xmx1300m -XX:MaxPermSize=270m.
  • Maximum settings that you will ever probably need are (x64 JVM should be used): -Xmx4g -XX:MaxPermSize=270m. These settings will suit for an installation with more than a hundred of agents and thousands of build configurations.
  • If you run TeamCity via runAll or teamcity-server scripts or via Windows service installed, the default settings used are: 512 Mb for the heap and 150 Mb for the PermGen.

To change memory settings, refer to Configuring TeamCity Server Startup Properties, or to the documentation of your application server, if you run TeamCity using .war distribution.


  • 32 bit JVM can use up to 1.3Gb memory. If more memory is necessary, 64 bit JVM should be used assigning not less than 2.5Gb. It's highly unlikely that you will need to dedicate more than 4Gb of memory to the TeamCity process.
  • A rule of thumb is that 64 bit JVM should be assigned twice as much memory as 32 bit for the same application. If you switch to 64 bit JVM please make sure you adjust the memory settings (both -Xmx and -XX:MaxPermSize) accordingly. It does not make sense to switch to 64 bit if you dedicate less than double amount of memory to the application.

The recommended approach is to start with initial settings and monitor for the percentage of used memory (see also TW-13452) at the Administration | Diagnostics page. If the server uses more then 80% of memory consistently without drops for tens of minutes, that is probably a sign to increase the memory values by another 20%.

Using 64 bit Java to Run TeamCity Server

TeamCity can run under both 32 and 64 bit JVM.
It is recommended to use 32 bit JVM unless you need to dedicate more than 1.3Gb of memory to the TeamCity process.

If you choose to use x64 JVM please note that the memory usage is almost doubled when switching from 32 to 64 bit JVM, so please make sure you specify at least twice as much memory as for 32 bit JVM, see #Setting Up Memory settings for TeamCity Server.

If you run TeamCity as a service and switch to x64 bit, you will also need to use x64 Tomcat executables, see more.

Configuring the TeamCity Server

  • If you have a lot of projects or build configurations, we recommend you avoid using the Default agent in order to free up the TeamCity server resources. The TeamCity Administrator can disable the default agent on the Agents page of the web UI.
  • When changing the TeamCity data directory or database make sure they do not get out of sync.

Configuring TeamCity Data Directory

The default placement of the TeamCity data directory can be changed. See corresponding section: TeamCity data directory for details.

Editing Server Configuration

After successful server start, any TeamCity page request will redirect to prompt for the server administrator username and password. Please make sure that no one can access the server pages until the administrator account is setup.

After administration account setup you may begin to create Project and Build Configurations in the TeamCity server. You may also want to configure the following settings in the Server Administration section:

  • Server URL
  • Email server address and settings
  • Jabber server address and settings

See also: