This page describes how to configure a Bitbucket Mercurial source repository for either a plan or a job.
Configuring a Bitbucket Mercurial Source Repository
To add a new Bitbucket 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.
- Click Add Repository.
- Choose Bitbucket from the Source Repository list.
- Add your Bitbucket Username and Password.
- You have the following options for specifying the source repositories for your plan:
| My Repositories | Retrieves all repositories you have explicit permissions to access from Bitbucket when you click Load Repositories. |
| URL | Allows you to specify a repository URL (eg. http://bitbucket.org/sindbad/ogre). To choose a branch to work with, other than the default branch, click Load Branches. |
| Branch | Pick a branch if you want to checkout code from a branch other than the default branch. |
Advanced Options
| Command timeout | This is useful to cut hung Bitbucket processes. On slower networks, you may consider increasing the default timeout to allow Bamboo time 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 this option if you encounter problems with Mercurial in Bamboo. |
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. ' 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. 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 Repository Generic Web Repository 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 — Bitbucket
Notes
- You will not be able to create plans or 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
Overview
Content Tools
Apps
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.