The instructions on this page describe how to configure a Bitbucket Mercurial source repository for either a Plan or a Job. | On this page: |
Configuring a Bitbucket 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 to add a new or edit an existing repository.
Once you've added your Bitbucket username and password, you will have the following options to specify the source repository for your plan
Repository | My Repositories | Retrieves all repositories you have explicit permissions to from Bitbucket once you click Load Repositories. |
URL | Select URL if you want to manually specify a repository URL (eg. http://bitbucket.org/sindbad/ogre). If you want to choose a branch to work on, other than the default branch, click Load Branches and select the desired branch. | |
Branches | Pick a branch if you want to checkout code from a branch other than the default branch. |
Advanced Options
Command timeout | Type the number of minutes bamboo should wait for Bitbucket commands to finish. This is useful to cut hung Bitbucket processes. On the slower networks, you may consider increasing the default timeout to allow Bamboo to make an initial clone of 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 Mercurial in Bamboo. |
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: 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 | Generic Web Repository | 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. | |
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 | 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. '
| ||
Build Strategy | 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. |
Screenshot above: Source Repository — Bitbucket
Notes
- The page Configuring a new Mercurial capability does not exist. You will not be able to create Plans/Jobs that use a Bitbucket Mercurial repository without specifying the shared local Mercurial capability first. Read more about configuring a Version Control capability.
Related Topics
Specifying the Source Repository for a Plan
Specifying the Source Repository for a Job
Attachments:


