Skip to end of metadata
Go to start of metadata

This page describes the fields and options available when setting up VCS roots using StarTeam.
Common VCS Root properties are described here.

StarTeam Connection Settings




Specify the StarTeam URL that points to the required sources


Enter the login for the StarTeam Server


Enter the corresponding password for the user specified in the field above

EOL Conversion

Define the EOL (End Of Line) symbol conversion rules for text files. Select one of the following:

  • As stored in repository — EOL symbols are preserved as they are stored in the repository. No conversion is done.
  • Agent's platform default — Whatever EOL symbol is used in a particular file in the repository, it will be converted to the platform-specific line separator when passed to the build agent. The resulting EOL symbol exclusively depends on the agent's platform.

Directory naming

Define the mode for naming the local directories. Select one of the following:

  • Using working folders — StarTeam folders have the "working folder" property. It defines which local path corresponds to the StarTeam folder (by default, the working folder equals the folder's name). In this mode TeamCity gives the local directories the names stored in the "working folder" properties. Please note that even though StarTeam allows using absolute paths as working folders, TeamCity supports relative paths only and doesn't detect the presence of absolute paths.
  • Using StarTeam folder names — In this mode the local directories are named after corresponding StarTeam folders' names. This mode can suit users who keep the working directory structure the same as the project structure in the repository and don't want to rely on "working folder" properties because they can be uncontrollably modified.

Checkout mode

Files can be retrieved by their current (tip) revision, by label, or by promotion state.
Note that if you select checkout by label or promotion state, change detection won't be possible for this VCS root. As a result, your builds cannot be triggered if the label is moved or the promotion state is switched to another label. The only way of keeping the build up-to-date is using the schedule-based triggering. To make it possible, a full checkout is always performed when you select checkout by label or promotion state options.

Notes on Directory Naming Convention

When checking out sources TeamCity (just as StarTeam native client) forms local directory structure using working folder names instead of just a folder name. By default, the working folder name for a particular StarTeam folder equals the folder's name.
For example, your project has a folder named "A" with a subfolder named "B". By default, their working folders are "A" and "B" correspondingly, and the local directory structure will look like <checkout dir>/A/B. But if the working folder for folder "A" is set to something different (for example, "Foo"), the directory structure will also be different: <checkout dir>/Foo/B.

StarTeam allows specifying absolute paths as working folders. However, TeamCity supports only relative working folders. This is done by design; all files retrieved from the source control must reside under the checkout directory. The build will fail if TeamCity detects the presence of absolute working folders.

You need to ensure that all the folders under the VCS root have relative working folder names.