This page describes how to configure Bamboo to use a Subversion 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.

On this page:

Configure a Subversion source repository

  1. Navigate to the repository configuration for a linked repository, plan or job. See Linking to source code repositories.
  2. Either click Add Repository to add a new repository, or edit an existing repository configuration.
  3. Choose Subversion from the Source Repository list.
  4. Enter a Display Name to help identify the repository in Bamboo.
  5. You can configure the following settings for a Subversion source repository for your plan:
Repository URL

The location of your Subversion repository e.g. Note that you can use global variables in this field (see Using Global or Build-specific Variables).

(info) If you are importing a Maven 2 Project, this location should contain your project's pom.xml file.

Username (Optional) The Subversion username (if any) required to access the repository.
Authentication Type 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:
    • Private Key — the absolute path of your SSH private key.
    • Passphrase — the passphrase for your SSH private key.

(info) 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:
    • Private Key — the absolute path of your SSL client certificate .
    • Passphrase — the passphrase for your SSL client certificate.

(info) 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.

Advanced Options

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.)
Include/Exclude Files

Allows you to specify the files that Bamboo should, or should not, use to detect changes.

Enter into File Pattern a regular expression to match the files that Bamboo  includes or excludes. The regex pattern must match the file path in the repository. See sub page for examples.

Exclude Changesets Enter a regular expression to match the commit messages for changesets that should not start a build.

Web Repository


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

    • Web Repository URL – the URL of the repository.
    • Web Repository Module — the particular repository required for this plan or job, if the Web Repository URL above points to multiple repositories.
Stash – specify the following details for the repository:
    • Stash URL – the URL of your Stash instance (e.g. '').
    • Stash Project Key – the key of the project in Stash (e.g. 'CONF').
    • Repository Name – the name of the repository in Stash (e.g. 'conf-dev').

See Integrating Bamboo with Stash for more information.

FishEye – specify the URL and other details for the repository:

    • FishEye URL — the URL of your FishEye repository (e.g. '').
    • Repository Name — the name of your FishEye repository (e.g. 'Bamboo'). This is effectively the alias for your repository path.
    • Repository Path — the path for your FishEye repository (e.g. '/atlassian/bamboo/').

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. 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.


  • If you are having problems connecting to Subversion, consult our documentation on troubleshooting Subversion connections.
  • If you use pre-1.5 Subversion client to access code checked out by Bamboo, you may encounter problems with your builds. This is due to the SVNKit upgrade in Bamboo 2.1.4. Please read this knowledge base article for further details.
  • You can add the -Dsvnkit.http.methods=Basic,NTLM system property to SVNKit to have NTLM authentication work with Bamboo.

Was this helpful?

Thanks for your feedback!

13 Archived comments

  1. User avatar

    Matt Doar (ServiceRocket)

    An example of a URL with a space in it would be good too.


    09 May 2008
  2. User avatar


    *Is it possible to specify more than one Repository URL? E.g., *http://abc/src/svn/unit1 and http://abc/src/svn/shared are both required to make a build.

    23 Mar 2009
    1. User avatar


      Any news on using multiple repository urls for product build?

      09 Apr 2010
      1. User avatar


        Yeah.  That would be great.

        18 Feb 2011
  3. User avatar


    The "Include /Exclude Files" option checks only file names, or absolute path, or path relative to working directory?

    16 Jun 2009
  4. User avatar


    Is it possible for a plan to share the same subversion checkout as another plan?. I need to perform extra operations in a generated ear file by a previous plan and it would be good to have access to those files.

    17 Jun 2009
  5. User avatar

    Terris Linenbach

    Desperately seeking example of an "exclude" or "include" regular expression. I'm a programmer and I know what a regex is, but I have no idea what Bamboo is trying to match it against.

    Let's cut to the chase. The file is something like http://foo/blank/trunk/harness/etc/env/ . What is the regex?

    21 Jul 2010
    1. User avatar

      Sam Kenny

      I raised this with Atlassian Support.  This is the reply from Renan which works for me:

      This field uses Java Regex. An example would be the following:

      That would exclude files located ate a path containing "/src/" or ending with ".txt".
      To exclude ".txt" files you can use:

      31 Aug 2010
  6. User avatar

    John Harelius

    In Bamboo 2.6 I could omit the username and password for accessing Subversion, and then the user running the Bamboo service was used. This was very convenient since you didn't need to bother about username and password for accessing Subversion when creating plans.

    I can't get this to work using Bamboo 2.7 though, have there been a change in the way subversion is accessed in Bamboo 2.7?

    18 Nov 2010
  7. User avatar


    For subversion SSH authentication the private key file must be in OpenSSH format.

    I run in windows and sa was trying to use a putty format key file (.ppk extension) and the error message wasn't very helpful. Fortunately the puttygen tool has the ability to save a key in OpenSSH format in "Conversions->Export OpenSSH key".

    25 Jul 2011
  8. User avatar

    Jijo John

    Is it possible to checkout/export multiple svn url's to same workspace for build?

    02 Sep 2013
    1. User avatar

      Chris Pettifer

      Yes, but you should use different checkout directories for them within the workspace.

      You configure your various repositories at the Plan level, then in the "Source Code Checkout" task you can use the "Add Repository" button to specify more than one repository location. But you must specify a "Checkout Directory" for all of your different checkouts (one can actually be blank, but it might be easier to put them all in directories).

      02 Sep 2013
  9. User avatar

    Wahid Atif

    Please vote.  BAM-14443 - SVN repository should support SSL client certificate + SVN credentials authentication Open

    25 Apr 2014
Powered by Confluence and Scroll Viewport