Label: directory

All content with label directory.
Related Labels: configure , concepts , vcs , role , configuration , data , working , clean , system , checkout , agent , build , upgrade , reference

Agent Working Directory (TeamCity 4.x Documentation)
Agent working directory is the directory on a build agent that is used as a containing directory for the checkout directories Build Checkout Directory. By default, this is the {{<Build agent home> Agent Home Directory/work}} directory. To modify the default directory location see Build Agent ...
Build Checkout Directory (TeamCity 4.x Documentation)
build checkout directory is the directory where all of the project's sources reside. If the {{VCS checkout mode}} property of the build configuration is set to Automatically on server or Automatically on agent, TeamCity places the sources into the checkout directory according to the mapping defined in the VCS Checkout ...
Build Checkout Directory (TeamCity 3.x Documentation)
Build Checkout Directory The build checkout directory is the directory where all of the project's sources reside. If the VCS checkout mode property of the build configuration is set to Automatically on server or Automatically on agent, TeamCity places the sources directly into the checkout directory. If not specified ...
TeamCity Data Directory (TeamCity 4.x Documentation)
directory used by TeamCity to store configuration and system files. The {{config}} subdirectory contains the configuration of your TeamCity projects, and the {{system}} subdirectory contains build logs, artifacts, and database files (if HSQLDB is being used by default). See more on the directory structure ...
TeamCity Data Directory (TeamCity 3.x Documentation)
TeamCity Data Directory This is the directory used by TeamCity to store configuration and system files. The {{config}} subdirectory contains the configuration of your TeamCity projects, and the {{system}} subdirectory contains build logs, artifacts, and database files (if HSQLDB is being used by default). See ...
Upgrade Notes (TeamCity 4.x Documentation)
page covers: Changes from 3.1.2 to 4.0 Initial startup time On the very first start of the new version of TeamCity, the database structure will be upgraded. This process can increase the time of the server startup. The first startup can take up to 20 ...
Upgrade Notes (TeamCity 3.x Documentation)
Upgrade Notes From 3.1.1 to 3.1.2 Users relogin will be forced after upgrade Upon upgrade, all users will be automatically logged off and will need to relogin in their browsers to TeamCity web UI. After the first login since upgrade, "remember me ...