[Bamboo Knowledge Base]
The instructions on this page describe how to configure Bamboo to use 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.
The location of your Subversion repository e.g.http://svn.collab.net/repos/svn/trunk Note that you can use global variables in this field (see Using Global or Build-specific Variables).
If you are importing a Maven 2 Project, this location should contain your project's
|(Optional) The Subversion username (if any) required to access the repository.
|Password – choose this option if you want to authenticate with a username and password.
|SSH – if you choose to authenticate using SSH, you need to provide the following details:
If you are planning to use remote agents the ssh private key file has to be copied to the agent box into the same location as specified.
|SSL Client Certificate – if you choose to authenticate using an SSL Client Certificate, you need to provide the following details:
Please note, the client certificate has to be in PKCS12 format and the client certificate file must be passphrase protected, otherwise a runtime exception is thrown by the JDK security engine while opening the user key.
|Detect Changes in Externals
Select this if your Subversion repository uses svn:externals to link to other repositories (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 reference a particular (static) revision, you do not need to check this box.
|Use SVN Export
|This option will speed up the first-time checkout, but updates are not supported. Implies Force Clean Build.
|Enable Commit Isolation
|Ensures that a build will only have one change, allowing you to isolate your build failures.
|Automatically detect root URL for branches
|Specifies whether the VCS Branching Task automatically determines the location of created branches.
|Automatically detect root URL for tags
|Specifies whether the VCS Tagging Task automatically determines the location of created branches.
|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. (Only available when configuring an existing plan.)
Allows you to specify the files that Bamboo should, or should not, use to detect changes.
|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
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.
-Dsvnkit.http.methods=Basic,NTLM system property to SVNKit to have NTLM authentication work with Bamboo.