This page describes how to configure Bamboo to use a Git 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.
You need to have previously defined a Git capability before you can configure a Git source repository – see Defining a new version control capability.
Note that Bamboo comes with its own built-in Git implementation. However, you need to use native Git to be able to use symbolic links, submodules, automatic branch detection and automatic merging - these are not supported by the built-in Git.
You can download Git from the following locations:
- Windows: http://code.google.com/p/msysgit/downloads/list?can=3&q=official+Git
- Linux and Mac: http://git-scm.com/download
Configure a Git 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 Git from the Source Repository list.
- Enter a Display Name to help identify the repository in Bamboo.
- You can configure the following settings for a Git source repository for your plan:
The full path to your Git repository (eg: )
Valid URLs are of the form:
|Branch||Type the name of the relevant branch (or tag) you want to work on. Leave empty to work on the |
|Authentication Type||None – choose none if you want to access the repository anonymously.|
|Username/password – authenticate with a username and password.|
|SSH private key – upload an SSH Key and provide the corresponding SSH Passphrase.|
|Use shallow clones|
Allows Bamboo to perform shallow clones (i.e. history truncated to a specified number of revisions). This should increase the speed of the initial code checkouts, however if your build depends on the full repository history, we recommend that you do not use this option. Shallow clones are enabled by default.
|Location of POM file|
The path to your project's
(Only available when importing a Maven 2 project)
|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.|
|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 Git repository.|
|Verbose logs||Turns on more verbose logs from Git commands. Use this option if you encounter problems with Git 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.|
Allows you to specify the files that Bamboo should, or should not, use to detect changes. When you configure the Include option, it means that you want Bamboo to use only the mentioned files for change detection because by default Bamboo checks all the files. The same way, if you configure the Exclude option, Bamboo will not consider the excluded files for detecting changes.
|Exclude Changesets||Enter a regular expression to match the commit messages for changesets that should not start a build.|
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.
|Stash – specify the following details for the repository:|
See Integrating Bamboo with Stash for more information.
FishEye – specify the URL and other details for the repository:
See Integrating Bamboo with FishEye for more information.
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.