This page describes how to configure Bamboo to use a Bitbucket Mercurial source repository for either a plan or a job.

Before you start:

  • 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 pages:

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.

  1. Either click Add Repository to add a new repository, or edit an existing repository configuration.
  2. Choose Bitbucket from the Source Repository list.
  3. Enter a Display Name to help identify the repository in Bamboo.
  4. Add your Bitbucket Username and Password.
  5. You can configure the following settings for a BitBucket source repository 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.
BranchPick a branch if you want to check out code from a branch other than the default branch.

Advanced Options

Command timeout This is useful to stop 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.
Enable Quiet PeriodSpecifies 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:

    • BitBucket Web Repository Scheme (if you use BitBucket)
    • Default Web Repository Scheme (hgserve) (Mercurial's own default web server)

FishEye – specify the URL and other details for the repository:

    • FishEye URL — the URL of your FishEye repository (e.g. ' https://atlaseye.atlassian.com/ ').
    • Repository Name — the name of your FishEye repository (e.g. 'Bamboo'). This is effectively the alias for your repository path.
    • Repository Path — the path for your FishEye repository (e.g. '/atlassian/bamboo/').

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. 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.