This page describes how to configure Bamboo to use a Bitbucket Cloud repository.

You can specify repositories at the following levels in Bamboo:

• global – repositories are available for all plans in Bamboo.
• plan – repositories are available for all jobs in the Bamboo plan.
• job – repositories are available for 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.

On this page:

Configure a Bitbucket source repository

1. Navigate to the repository configuration for a linked repository, plan, or job. See Linking to source code repositories.
2. Either select Add repository to add a new repository, or edit an existing repository configuration.
3. Select Bitbucket Cloud from the Source repository list.
4. Enter a Name to help identify the repository in Bamboo.
5. Specify the repository access level and corresponding authentication details for loading the list of repositories:
   

   
   

   Step	Public	Private
   5.1	Provide the name of the Bitbucket Cloud user who owns the repository in the Owner field.	To load the list of repositories available in Bitbucket Cloud you can provide a username and an app password or use shared credentials.
   5.2	You can configure the following settings of a public or private source repository for your plan: Repository - retrieves all repositories you have explicit permissions to access from Bitbucket Cloud when you select Load repositories Branch - pick a branch if you want to check out code from a branch other than the default branch
   5.3		For private repositories, you can specify the authentication method that Bamboo will use to connect to the repository you selected. You can choose from: App password - create an app password SSH private key - provide an SSH key to authenticate; use shared credentials or upload an SSH key and type a passphrase Bitbucket password - if you created your Atlassian account before September 13, 2021, reuse the credentials provided in step 5.1; see Deprecating Atlassian account password for Bitbucket API and Git activity for more information
   5.4	The Enable webhooks flag determines whether the source repository will use the webhook-based integration of Bamboo with Bitbucket Cloud. Enabling the flag results in the following behavior: Plans using this repository default to using the Bitbucket Cloud repository trigger instead of the polling trigger Branch and pull request detection relies on webhook events rather than polling Enhanced plan branch configuration with Bamboo Specs becomes available Webhook registration is enabled on the repository configuration screen and allows to set up the integration in Bitbucket Cloud

Advanced Options

Use submodules
Select to enable submodules support if these are defined for the repository. If native Git capability is not defined for agent submodules support will be disabled.

SSH key applies to submodules
Bamboo will use the primary repository's SSH key for submodule authentication.

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 --verbose and --debug options in Hg or Git commands and passes the output to build logs. Use this option if you encounter problems with Git or Mercurial in Bamboo.

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 subpage for examples.

Exclude changesets
Enter a regular expression to match the commit messages for changesets that should not start a build.

Git LFS 

To learn more about Git LFS, see Git LFS tutorials.

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 Unable to locate Jira server for this macro. It may be due to Application Link configuration. for more information.

Fisheye – specify the following details for the repository:

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

See Integrating Bamboo with Fisheye for more information.

Bitbucket Cloud and Bamboo webhook integration

Learn how to configure triggering a build from Bitbucket Cloud using webhooks that enables change, branch, and pull request detection. With the integration, you can use branch divergence.

Bamboo statuses in Bitbucket Cloud

You can view the status of Bamboo builds in Bitbucket Cloud.

The feature is setup automatically if you setup a plan in the following way:

• the repository type is Bitbucket Cloud or Bitbucket Server
• you provided Bitbucket credentials (username and app password)

The automatic setup of Bamboo build statuses in Bitbucket works with private and public repositories as long as you provide valid Bitbucket credentials.

The build statuses in Bitbucket are displayed in the commit, branch, and pull request views.

For more information about Bamboo statuses in Bitbucket Cloud, see:

• Pull requests and code review
• Integrate your build system with Bitbucket Cloud
• statuses/build Resource