The instructions on this page describe how to configure a Git source repository. | On this page: |
Configuring a Git Source 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 and select Git in the Source Control drop-down.
Git gives you the following options:
Repository URL | Type the full path to your Git repository (eg: git://github.org/atlassian/bamboo-git-plugin.git) 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 master branch. | |
Authentication Type | None | Choose none if you want to access the repository anonymously. |
Password | Choose password if you want to authenticate with a username and password. | |
SSH private key | Upload a private key and provide the corresponding SSH Passphrase. | |
Use shallow clones | Select this setting to allow 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 | Type the path to your project's (Only available when importing a Maven 2 project) |
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: 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 | Generic Web Repository | 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. | |
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 | 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. '
| ||
Build Strategy | 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. |
Screenshot: Source Repository — Git
Notes
Related Topics
Specifying the Source Repository for a Plan
Specifying the Source Repository for a Job