TeamCity Data Directory
note
Note that the
system
directory stores all the Build Artifact of the builds in the history and can be quite large, so it is recommended to place TeamCity Data Directory on a non-system disk. Please also refer to Clean-Up section to configure automatic cleaning of older builds.
tip
If you run TeamCity as Windows service installed via Installing and Configuring the TeamCity Server from the Windows executable file, you will need to modify the
teamcity.data.path
Tomcat JVM property as described in TeamCity Startup Properties. Modifying theTEAMCITY_DATA_PATH
environment variable will not work in this case.
Structure of TeamCity Data Directory
Direct configuration files modifications
note
Please note that there are interlinking entries that link by id. Examples of such entries are build configuration -> VCS roots links and VCS root -> project links. All the entries of the same type must have unique ids. New entries can be added only if their ids are unique.
note
Please note that it is not a good idea to place TeamCity data directory to a network folder. Such folders may disappear if network failure occurs and TeamCity may decide that projects deleted and unload them. If you really need to place data directory to such folder, we strongly recommend to disable files modifications monitoring by launching TeamCity with special system property (available since 3.1.1): teamcity.configuration.checkInterval. Set this property to -1 to disable changes checking, positive value defines changes checking interval in seconds.
Thanks for your feedback!