This page describes how to configure a Mercurial source repository.
要件
- Please use Mercurial 2.1.1 or later. Mercurial 2.1 has a bug that makes it incompatible with Bamboo.
Configuring a Mercurial Source Repository
Navigate to the source repository settings for a Plan or Job, as described on Specifying the Source Repository for a Plan. Choose whether to add a new repository, or edit an existing repository, and select Mercurial in the Source Control drop-down.
Mercurial gives you the following options:
| リポジトリ URL | Type the full path to your Mercurial repository (eg: git://bitbucket.org/atlassian/bamboo-git-plugin.git) 有効な URL の形式は次のとおりです。
(for further references visit Mercurial documentation) | |
| ブランチ | Type the name of the relevant branch (or tag) you want to work on. Leave empty to work on default branch. | |
| ユーザ名 | Type the username (if any) required to access the repository. | |
| 認証タイプ | パスワード | Choose password if you want to authenticate with a username and password. |
| Keyfile with passphrase (パスフレーズのあるキーファイル) | Upload a private key and provide the corresponding SSH Passphrase. | |
| Keyfile without passphrase (パスフレーズのないキーファイル) | This type of authentication is similar to Keyfile with passphrase. However, authenticating without a passphrase is a bit faster. You will still have to Upload a private key. | |
| Default Mercurial credentials (既定の Mercurial 資格情報) | Bamboo では、既定の hg 認証が使用されます。このオプションは、たとえば .ssh/config で定義されている SSH サーバーや有効な SSH ID ファイルなどを使用して手動で Bamboo サーバーを設定した場合に使用します。 | |
詳細オプション
| コマンド タイムアウト | Type the number of minutes bamboo should wait for hg commands to finish. This is useful to cut hung Mercurial processes. On the slower networks you may consider increasing default timeout to allow bamboo making initial clone of mercurial repository. | |
| 詳細なログ | Turns on --verbose and --debug options in hg commands and pass the output to build logs. Use that option if you encounter problems in Bamboo Mercurial behaviour. | |
| POM ファイルの場所 | (上記で定義した) Mercurial の [リポジトリ URL] のルートを基準にして、プロジェクトの (Maven 2 プロジェクトをインポートする場合にのみ利用可能) | |
File Pattern — The regular expression for file changes which you wish to include/exclude. The regex pattern must match the file path in the repository. Visit sub page for a few examples. Web Repository URL — If your source repository can be accessed via a web browser, you can specify the URL of the source repository here. If you specify a Web Repository URL, then links to relevant files will be displayed in the 'Code Changes' section of a build result. Web Repository Module — The repository name of the Plan/Job, if the above Web Repository URL points to multiple repositories. FishEye URL — The URL of your FishEye repository (e.g. ' Repository Name — The name of your FishEye repository (e.g. ' Repository Path — The path for your FishEye repository (e.g. ' リポジトリのパスを特定する方法 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. Choose one of the build strategy options (listed below), which will be used for triggering the execution of this Plan. You can change the Build Strategy at a later point in time as required. Common Repository Configuration
Force Clean Build (クリーン ビルドを強制) You can force Bamboo to remove the source directory and check it out again prior to the Plan/Job build being built by selecting this option. Please note that this will greatly increase the time it takes to complete a build. Clean working directory after each build You can force Bamboo to remove the source directory after the Plan/Job is completed building by selecting this option. Please note that this may increase build times but saves on disk space. Include/Exclude Files (ファイルを含める/除外する) You can specify a particular inclusion or exclusion pattern for file changes to be detected. If you select an option other than 'None', the following field will appear: Web リポジトリ 一般的な Web リポジトリ Mercurial Web Repository Choose between using the BitBucket Web Repository Scheme (if you use BitBucket) or Mercurial's own default web server Default Web Repository Scheme (hgserve). FishEye https://atlaseye.atlassian.com/').Bamboo'). This is effectively the alias for your repository path./atlassian/bamboo/').trunk)). For example, if a code change listed /atlassian/bamboo/trunk/bamboo-acceptance-test/pom.xml, the path would be /atlassian/bamboo/.
If you have not previously run builds with changes from your repository, you will need to ask your FishEye administrator for the repository path indexed by FishEye. Build Strategy 
You may need to configure other options specific to your chosen build strategy. If you select Manual & dependent builds only when creating a new Plan, an initial build will not automatically be run. You can force an initial build to be executed automatically by adding the fire.initial.build.for.manual.strategy to your bamboo.cfg.xml file as described in Configuring System Properties.
Screenshot: Source Repository — Mercurial
注意
- You will not be able to create Plans/Jobs that use a Mercurial repository without specifying the shared local Mercurial capability first. Read more about configuring a Version Control capability.
関連トピック
Specifying the Source Repository for a Plan
Specifying the Source Repository for a Job
概要
コンテンツ ツール
アプリ
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.