TeamCity
 
3.0
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. System Administrator Reference
  3. System Properties for Running the Server

System Properties for Running the Server

Last modified: 20 April 2023

Various aspects of TeamCity's behavior can be customized through a set of JVM options. The options can be specified using the -D parameter passed to the JVM running the TeamCity server or agent. e.g.

-Dteamcity_logs=../logs/

tip

  • If you run the server using the runAll or teamcity-server scripts, you can set the options via TEAMCITY_SERVER_OPTS environment variable.

  • If you run the server as Windows service, run Tomcat's service configuration editor by executing the command tomcat6w.exe //ES//TeamCity in <TeamCity home>\bin directory and then editing the Java Options on the Java tab (for more information see Tomcat 6 documentation).

You will need to restart the server for the option to take effect.

Server-only Properties



Property Name

Description

teamcity.data.path

You can edit this property to modify default location of TeamCity data directory. Please note that the recommended way to change the location is to use environment variable.

modification.check.interval

Number of seconds between successive polling of VCS servers (TeamCity 3.0 has a default value of 60). The interval's time starts being counted as soon as the last VCS server poll is finished. Since TeamCity 3.0 this property can be edited in the web UI on Administration > Server Configuration page

Server and Agent Properties



Property Name

Description

log4j.configuration

The URL of the log4j.xml file to be used for logging in TeamCity (applies both to agent and server). For example:

-Dlog4j.configuration=file:../conf/teamcity-server-log4j.xml

teamcity_log

When the default teamcity-(server/agent)-log4j.xml is used, this specifies the directory which will contain TeamCity logs. By default it points to <TeamCity home>/logs or <TeamCity Agent home>/logs, respectively.

Other Server Configurations



Turning off code highlighting in the web diff



The highlighting uses a third-party native library that may not be available for your platform. If TeamCity fails to cope with this or the library causes unstable behavior on the server, you can disable the use of this library.

To disable the Colorer library:

  1. Edit <TeamCity Home>\webapps\ROOT\WEB-INF\buildServerSpringWeb.xml and change the "enableColorer" property value to false by locating the following fragment: <property name="enableColorer" value="true"/> and changing it to <property name="enableColorer" value="false"/>

  2. Restart the server.