TeamCity
 
7.0
You are viewing the documentation for an earlier version of TeamCity.
  1. TeamCity Documentation
  2. Administrator's Guide
  3. Managing Projects and Build Configurations
  4. Creating and Editing Build Configurations
  5. Configuring VCS Settings
  6. Configuring VCS Roots
  7. ClearCase

ClearCase

Last modified: 20 April 2023

This page contains description of the fields and options available when setting up VCS roots using the ClearCase Version Control System:

Initial Setup



First of all you need to have an installed ClearCase client on TeamCity server to make TeamCity CleaCase integration work. You also need to create a ClearCase view on TeamCity server machine (no matter whether you plan to use server-side or agent-side checkout). This view will be used for collecting changes in ClearCase VCS roots and for checkout in case of server-side checkout mode. In case of agent-side checkout mode config spec of this view will be also used to automatically create views on agents.

tip

If you plan to use agent-side VCS Checkout Mode, make sure ClearCase client (cleartool) is also installed on agents and properly configured, i.e. the tool must be in system paths and have access to the ClearCase Registry.

ClearCase Settings



Option

Description

ClearCase view path

Local path on the TeamCity server machine to the ClearCase view created during the Initial+Setup. Snapshot view is preferred as there is no benefit in using dynamic view with TeamCity. Also, dynamic views are not supported for agent-side checkout (TW-21545).

note

Do not use the view you are currently working with. TeamCity calls update procedure before checking for changes and building patch, and thus it might lead to problems with checking in changes.

Relative path within the view

Path relative to the "ClearCase view path" that limits the sources to watch and checkout for the build.

Branches

Branches are used in "-branch" parameter for "lshistory" command to significally improve its performance. You can either let TeamCity detect the needed branches automatically (via view's config spec) or specify your own list of needed branches. Press "Detect now" button to see the branches those TeamCity automatically detects. You can also choose "use custom" option and leave the text field blank - then "-branch" parameter will not be used for "lshistory" command at all. If you specify or TeamCity detects several branches, then "lshistory" will be called for every branch and all results will be merged.

Use ClearCase

Use the drop-down menu to select either UCM or BASE.

Global labeling

Check this option if you want to use global labels

Global labels VOB

Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted)

tip

Make sure that the user that runs the TeamCity server process is also a ClearCase view owner.

Changes Checking Interval



Option

Description

Checking interval

Select here how often TeamCity should check for VCS changes. By default the global predefined server setting is used, that can be modified at the Administration | Global Settings page. The interval's time starts being counted as soon as the last VCS server poll is finished. Here you can specify here custom interval for the current VCS root.

note

Some public servers can block access if polled frequently.

VCS Root Sharing



Option

Description

VCS Root Sharing

Enable this option to use this VCS root in other projects or build configurations. See Configuring VCS Roots for more information.