All Versions
Bamboo 5.13Bamboo 5.7.x
Bamboo 5.6.x
More...
The instructions on this page describe how to configure a Subversion source repository.
On this page:
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 Subversion in the Source Control drop-down.
Subversion gives you the following options:
Repository URL | The location of your Subversion repository (e.g.http://svn.collab.net/repos/svn/trunk)
| |
Authentication Type | Password | Choose this option if you want to authenticate with a username and password. |
SSH | If you choose to authenticate via SSH, you will have to provide the following details: Private Key — The absolute path of your SSH private key
| |
SSL Client Certificate | If you choose to authenticate via SSH, you will have to provide the following details: Private Key — The absolute path of your SSL client certificate
|
Quiet Period | Select this setting to set Quiet Period parameters for the Plan's build. Upon selecting this option, the following fields become available: Quiet Period — This field will only display if 'Enable Quiet Period:' has been selected. 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. Maximum Retries — You can specify how many times Bamboo should check for new changes using the Quiet Period parameter before initiating a build. For example, if you have set the 'Quiet Period' to '10' seconds then Bamboo will check if a checkout has occurred in the last 10 seconds. If you have then specified 'Maximum Retries:' as '5', then Bamboo will perform this check five times before initiating the build, regardless of any activity during the Quiet Period of the last check. (Only available when configuring an existing Plan) | |
Detect Changes in Externals | Select this check box if your Subversion repository uses svn:externals to link to other repositories (note that your externals must be in the root of the checkout directory, not in a subdirectory). Please note that you only need to select this check box if you require Bamboo to detect changes in the externals. If your externals references a particular (static) revision, you do not need to check this box. |
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. 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. 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. ' 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. 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. 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: Web Repository Generic Web Repository 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 https://atlaseye.atlassian.com/
').Bamboo
'). This is effectively the alias for your repository path./atlassian/bamboo/
').trunk
)). For example, if a code change listed /atlassian/bamboo/trunk/bamboo-acceptance-test/pom.xml
, the path would be /atlassian/bamboo/
.
If you have not previously run builds with changes from your repository, you will need to ask your FishEye administrator for the repository path indexed by FishEye.Build Strategy You may need to configure other options specific to your chosen build strategy.
If you select Manual & dependent builds only when creating a new Plan, an initial build will not automatically be run. You can force an initial build to be executed automatically by adding the
fire.initial.build.for.manual.strategy
to your bamboo.cfg.xml
file as described in Configuring System Properties.
Screenshot above: Source Repository — SVN
Specifying the Source Repository for a Plan
Specifying the Source Repository for a Job