Bitbucket
This page describes how to configure Bamboo to use a Bitbucket 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.
Note that you will not be able to create plans or jobs that use a Bitbucket repository without first specifying the shared local Mercurial or Git capability. Read more about configuring a Version Control capability.
Configure a Bitbucket 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 Bitbucket from the Source Repository list.
- Enter a Display Name to help identify the repository in Bamboo.
- Add your Bitbucket Username and Password.
- You can configure the following settings for a Bitbucket source repository for your plan:
Repository | Retrieves all repositories you have explicit permissions to access from Bitbucket when you click Load Repositories. |
Branch | Pick 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 | For Mercurial: Turns on |
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. |
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. Note: This option is not available for Git repositories. See - BAM-13376Getting issue details... STATUS for more information. |
Mercurial Web Repository – select one of the following viewer schemes:
| |
Stash – specify the following details for the repository:
| |
FishEye – specify the following details for the repository:
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. |