[Bamboo Knowledge Base]
You can specify repositories at the following levels in Bamboo:
The recommended approach is to set up linked source repositories at the global level – see Linking to source code repositories.
The full path to your CVS repository root (e.g.
If you are importing a Maven 2 Project, this location should contain your project's
|Authentication Type||Password – choose this option if you want to authenticate with a password.|
|SSH – if you choose to authenticate using SSH, you need to provide the following details:|
This setting is used to avoid starting a build while someone is in mid-checkin. Bamboo will only initiate a build for this plan when no more changes are detected within the Quiet Period following the last known change. Type the number of seconds Bamboo should wait. Please note that this parameter is mandatory for CVS, as CVS allows partial checkouts.
(Only available when configuring an existing plan)
Type the name of the CVS module that contains the source-code.
Currently Bamboo has limited support for CVS ampersand modules. To use an ampersand module, you will need to define a regular module with the same name as the ampersand module (since Bamboo expects there to be a directory with the specified checkout module name). For example:
|Version of module|
The version of the module that Bamboo should build:
Note that you can use global variables in this field (see Bamboo variables).
Allows you to specify the files that Bamboo should, or should not, use to detect 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.
Generic Web Repository
|Stash – specify the following details for the repository:|
See Integrating Bamboo with Stash for more information.
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.