Enter the location of your mercurial repository. This is the value of the SOURCE parameter that gets passed to the clone command line option. For instructions on how to get Continua working with a SSH mercurial repository, see Mercurial over SSH.
Examples:
C:\my_hg_repo
\\server\share\hg_repo
http://www.mydomain.com/hg_repo
ssh://user@server//home/projects/alpha/
If your repository requires a username, enter it in the Username field.
If your repository requires a password, enter it in the Password field.
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the Mercurial plugin. The pattern for this action is ^mercurial\..*
If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "Mercurial".
For more in-depth explanations on property collectors see Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
There are 3 options to choose from when selecting which branch(es) to monitor.
Tick to take case into account when matching the branch against the branch pattern.
Tick to hide inactive branches from Start Build and Trigger dialogs.
You can also specify a maximum branch age. This allows you to exclude older branches from the selection list when starting a new build or defining a trigger.
Choose how to deal with tagged commits. You can choose to Ignore tags completely, Detect tags and show then next to changesets, or Detect and list as new changeset . The later option will create a new changeset in the database representing that a tag change (new tag, tag deletion or modification) was made. This new changeset can be used to trigger a build.
Normally only the latest changeset on each branch is loaded into the database when the repository is initialised. When this option is ticked earlier changesets which are the source of a tag are also loaded during initialisation. All tags are then available to be selected when starting a build.
An alternative username for committing tag changes to the hg repository. Leave blank to use the main repository Username.
An alternative password for committing tag changes to the hg repository. Leave blank to use the main repository Password.
Allow insecure (such as self-signed) SSL certificates.
The code page to use when running hg commands. Leave blank to use default Windows code page.
Use UTF8 when running hg commands.
Tick to write changeset details to the file "_CI_ChangesetDetails.xml" after checking out each changeset.