TeamCity
 
2.1
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. TeamCityReference
  3. Reference
  4. Administrator's Reference
  5. 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 script, edit the script to include this option. If you run the server as Windows service, run Tomcat's service configuration editor by entering the command TeamCity/bin/tomcat6w.exe //ES//TeamCity and edit the Java Options on the Java tab

Server-only Properties



Property Name

Description

teamcity.data.path

Specifies the location of configuration and system directories for TeamCity. config directory will contain configuration of your TeamCity projects, system directory will contain build logs, artifacts, and database files (for HSQLDB database). The default value of this property is $HOME/.BuildServer. You can also use TEAMCITY_DATA_PATH environment variable to specify this directory.

modification.check.interval

Number of seconds between successive polling of VCS servers (TeamCity 2.1 has a default value of 60, whereas it was 30 in TeamCity 2.0). The interval's time starts being counted as soon as the last VCS server poll is finished.

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). e.g. -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/logs or buildAgent/logs, respectively.