Icon

You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.1 documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Option

Description

Pull changes from

The URL of your hosting.

Anchor
defaultBranch
defaultBranch
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.

Note

Bookmarks support requires Mercurial 2.4 installed on the TeamCity server.

Use tags as branches

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

Wiki Markup
{hidden-data}
| Clone repository to      | Clones the repository structure. Provide the path to a parent directory on the TeamCity server where a cloned repository will be created (applicable to the ["Automatically on server"|VCS Checkout Mode#ServerCheckout] checkout mode only). Leave blank to use the default path. |{hidden-data}

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.

Anchor
hgpath
hgpath

HG command path

The path to the hg executable. Used on TeamCity server only if included into whitelist. See more below.

 

Anchor
cloneto
cloneto

Anchor
hgDetection
hgDetection

...

During the build, the plugin uses the hg specified in the HG command path field of a VCS root settings. To use the detected hg, put %teamcity.hg.agent.path% in this field. Configurations with such settings will be run only on agents which report the path to hg.

Starting with Since TeamCity 2017.2.2,  the server side of the plugin checks the value of the teamcity.hg.customServerHgPathWhitelist internal property. The property contains the ;-separated list of allowed hg paths to use on the server.  If the path specified in VCS root is in whitelist, then it is used on the server. If not, the path specified in the teamcity.hg.server.path internal property is used. If this property is not set, TeamCity server uses hg from the $PATH.

...

Property

Default

Description

teamcity.hg.pull.timeout.seconds

3600

Maximum time in seconds for pull operation to run

teamcity.hg.server.path

hg

Path to the hg executable on the server (see Path to hg executable detection for the details).

teamcity.hg.customServerHgPathWhitelist ;-separated list of allowed paths to hg executable to use on TeamCity server machine

...

Property

Default

Description

 

Wiki Markup
{hidden-data}
| teamcity.hg.use.local.mirrors         | false    | When checkout on agent: whether TeamCity should clone to local agent mirror first and then clone to working directory from this local mirror. This option speeds up a clean checkout, because only build working directory is cleaned. Also if single root is used in several build configurations a clone will be faster. |{hidden-data}
 

teamcity.hg.pull.timeout.seconds

3600

Maximum time in seconds for pull operation to run

teamcity.hg.agent.path

hg

Path to hg executable on the agent (see Path to hg executable detection for the details).

 

See also:

...