System Properties for Running the Server
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/
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 |
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 |
teamcity_log | When the default |
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:
Edit
<TeamCity Home>\webapps\ROOT\WEB-INF\buildServerSpringWeb.xml
and change the "enableColorer
" property value tofalse
by locating the following fragment:<property name="enableColorer" value="true"/>
and changing it to<property name="enableColorer" value="false"/>
Restart the server.