This page describes how to configure Bamboo to use a Mercurial repository.
You can specify repositories at the following levels in Bamboo:
- global – repositories are available to all plans in Bamboo.
- plan – repositories are available to all jobs in the Bamboo plan.
- job – repositories are available to all tasks in the Bamboo job.
The recommended approach is to set up linked source repositories at the global level – see Linking to source code repositories.
- Please use Mercurial 2.1.1 or later. Mercurial 2.1 has a bug that makes it incompatible with Bamboo.
- You will not be able to create plans or jobs that use a Mercurial repository without specifying the shared local Mercurial capability first. Read more about configuring a version control capability.
Configure a Mercurial source repository
- Navigate to the repository configuration for a linked repository, plan or job. See Linking to source code repositories.
- Either click Add Repository to add a new repository, or edit an existing repository configuration.
- Choose Mercurial from the Source Repository list.
- Enter a Name to help identify the repository in Bamboo.
- You can configure the following settings for a Mercurial source repository for your plan:
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)
|ブランチ||The name of the relevant branch (or tag) you want to work on. Leave empty to work on default branch.|
|認証||Username and password||
You can use shared credentials or type a username and a password.
|SSH private key||
You can use shared credentials or upload an SSH key and provide the SSH passphrase.
|SSH private key (direct connection)||Upload an SSH Key. The passphrase is not required.|
|Default Mercurial credentials||Bamboo will rely on the default hg authentication. Use this option, for example, if you had set up the Bamboo server manually with SSH servers defined in
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
|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.|
Allows you to specify the files that Bamboo should, or should not, use to detect changes.
|Exclude Changesets||ビルドを開始しないチェンジセットのコミット メッセージに合うように正規表現を入力します。|
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:
Use this option to connect to a Bitbucket Server repository.
See Integrating Bamboo with Bitbucket Server for more information.
FishEye – リポジトリの URL およびその他の詳細を指定します。
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.