[Bamboo Cloud docs]
[Bamboo Knowledge Base]
This page describes how to configure Bamboo to use a Mercurial repository.
You can specify repositories at the following levels in Bamboo:
The recommended approach is to set up linked source repositories at the global level – see Linking to source code repositories.
Before you start:
Related pages:
Repository URL | The full path to your Mercurial repository (eg: git://bitbucket.org/atlassian/bamboo-git-plugin.git) Valid URLs are of the form:
(for further references visit Mercurial documentation) | |
Branch | The name of the relevant branch (or tag) you want to work on. Leave empty to work on default branch. | |
Username | The username (if any) required to access the repository. | |
Authentication | Password | Choose Password if you want to authenticate with a username and password. |
Keyfile with passphrase | Upload an SSH Key and provide the corresponding SSH Passphrase. | |
Keyfile without passphrase | Upload an SSH Key . | |
Default Mercurial credentials | Bamboo will rely on default hg authentication. Use this option, for example, if you had set up the Bamboo server manually with SSH servers defined in .ssh/config , valid SSH identity files, etc. |
Advanced Options
Command timeout | Type the number of minutes bamboo should wait for hg commands to finish. This is useful to stop hung Mercurial processes. On slower networks you may consider increasing default timeout to allow Bamboo to make an initial clone of the Mercurial repository. | |
Verbose logs | Turns on --verbose and --debug options in hg commands and passes the output to build logs. Use that option if you encounter problems with Mercurial in Bamboo. | |
Location of POM file | Type the path to your project's (Only available when importing a Maven 2 project) | |
Disable repository caching | Select this option to enable subrepositories support. | |
Enable Quiet Period | Specifies a delay after a single commit is detected before the build is started. This allows multiple commits to be aggregated into a single build. | |
Include/Exclude Files | Allows you to specify the files that Bamboo should, or should not, use to detect changes. Enter into File Pattern a regular expression to match the files that Bamboo includes or excludes. The regex pattern must match the file path in the repository. See sub page for examples. | |
Exclude Changesets | Enter a regular expression to match the commit messages for changesets that should not start a build. | |
Web Repository | If your repository can be viewed in a web browser, select the repository type. This allows links to relevant files to be displayed in the 'Code Changes' section of a build result. | |
Mercurial Web Repository – select one of the following viewer schemes:
| ||
Stash – specify the following details for the repository:
See Integrating Bamboo with Stash for more information. | ||
FishEye – specify the URL and other details for the repository:
See Integrating Bamboo with FishEye for more information. How do I determine my Repository Path? If you have previously run builds with changes from your repository, the easiest way of determining your repository path is to view the code changes and copy the path from the start of the path of one of the changed files, up to (but not including) the appropriate root directory. The root directories for repositories are the ones shown by FishEye when browsing a repository (e.g. |