TeamCity Cloud 2023.09 Help

Mercurial

TeamCity uses the typical Mercurial command line client: hg command. Mercurial 1.5.2+ is supported.

Note that:

  • Remote Run from IDE is not supported. Please use Branch Remote Run Trigger instead.

  • Checkout rules for agent-side checkout are not supported except for the .=><target_dir> rule.
    For common VCS Root properties, see this section. The section below contains the description of Mercurial-specific fields and options.

TeamCity supports Mercurial out of the box.

General Settings

Option

Description

Pull changes from

The URL of your hosting.

Default branch

Set to the default branch which used in the absence of branch specification or when the branch of the branch specification cannot be found. Note that parameter references are supported here.

Branch specification

In this area list all the branches you want to be monitored for changes. The syntax is similar to checkout rules: +|-:branch_name, where branch_name is specific to the VCS (with the optional * placeholder). Note that only one asterisk is allowed and each rule has to start with a new line. Bookmarks can also be used in the branch and branch specification fields. If a bookmark has the same name as a regular branch, a regular branch wins. More in the related TeamCity blogpost.

Use tags as branches

Allows you to use tags in branch specification. By default, tags are ignored.

Detect subrepo changes

By default, subrepositories are not monitored for changes.

Username for tags/merge

A custom username used for labeling

Use uncompressed transfer

Uncompressed transfer is faster for repositories in the LAN.

Agent Settings

These are the settings used in case of the agent-side checkout (default mode), which requires Mercurial installed on all agents.

Option

Description

Mercurial config

Specify the Mercurial configuration options to be applied to the repository during agent-side checkout, for example, enter the following to enable the largefiles extension:

[extensions] `largefiles =

The configuration format is described here.

Purge settings

Defines whether to purge files and directories not being tracked by Mercurial in the current repository. You can choose to remove only unknown files and empty directories, or to remove ignored files as well. Added files and (unmodified or modified) tracked files are preserved.

Use mirrors

When enabled, TeamCity creates a local agent mirror first (under agent's system/mercurial directory) and then clones to the working directory from this local mirror. This option speeds up clean checkout, because only the build working directory is cleaned. Also, if a single root is used in several build configurations, a clone will be faster.

Last modified: 07 September 2023