Where Does TeamCity Store Data?
TeamCity keeps builds, artifacts and config in its data directory on Linux. The data root and what to back up.
Last updated
TeamCity centers on a data directory holding config, the database, build logs and artifacts. The install folder only carries the application. Upgrades replace the application side while data persists.
That split keeps updates safe when honored. Pointing a new version at a copied data directory migrates settings forward. Mixing versions across the copy corrupts the database, so match releases exactly.
Where TeamCity stores this, by platform
~/.BuildServer/
Default data root with config, database, logs and artifacts below it. The TEAMCITY_DATA_PATH variable relocates it, and Docker images mount it as a volume instead. Stop the server before copying; check the admin diagnostics page for the active path when unsure.
Frequently asked questions
How do I back up TeamCity?
Back up the data directory with the server stopped, especially config, database and artifacts trees. Builds, history and settings travel together. Restore to a matching TeamCity version before starting the service.
Where are build artifacts?
In the artifacts tree under the data directory per build. Logs sit beside them. Artifacts outside retention rules clean automatically, so pin important builds before relying on file copies.
Notice an outdated path? Let us know.