Documentation for Bamboo 4.1.x. Documentation for earlier versions of Bamboo is available too.

The instructions on this page describe how to configure Bamboo to use a Subversion source repository.

On this page:

Related pages:

Configuring a Subversion source repository

Navigate to the source repository settings for a plan or job, as described on Specifying the source repository.

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

The location of your Subversion repository e.g.http://svn.collab.net/repos/svn/trunk(info) 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 ExportThis option will speed up the first-time checkout, but updates are not supported. Implies Force Clean Build.
Enable Commit IsolationEnsures that a build will only have one change, allowing you to isolate your build failures.
Automatically detect root URL for branchesSpecifies whether the VCS Branching Task automatically determines the location of created branches.
Automatically detect root URL for tagsSpecifies 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 ChangesetsEnter 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. 'https://stash.mycompany.com').
    • 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. 'https://atlaseye.atlassian.com/').
    • 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.

Notes

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

11 Comments

  1. MattS

    May 09, 2008

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

    E.g. http://svn.collab.net/repos/svn/trunk/directory%20with%20spaces

  2. Anonymous

    Mar 23, 2009

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

    1. Anonymous

      Apr 09, 2010

      Any news on using multiple repository urls for product build?

      1. Anonymous

        Feb 18, 2011

        Yeah.  That would be great.

  3. Anonymous

    Jun 16, 2009

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

  4. Anonymous

    Jun 17, 2009

    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.

  5. Terris Linenbach

    Jul 21, 2010

    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/info.pm . What is the regex?

    1. Sam Kenny

      Aug 31, 2010

      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:

      .*/src/.*|.*\.txt

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

      .*\.txt

  6. John Harelius

    Nov 18, 2010

    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?

  7. Anonymous

    Jul 25, 2011

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

  8. Anonymous

    Apr 18, 2012

    Other man live to eat, while I eat to live.Patience! The windmill never strays in search of the wind.dkjferere66 The jealous are troublesome to others, but a torment to themselves.


    <strong><a href="http://www.2012-cap.com">Cheap Snapback Hats</a></strong><br>
    <a href="http://www.2012-cap.com">Snapback Hats Wholesale</a><br>
    <a href="http://www.2012-cap.com">Cheap New Era Hats&Caps</a><br>
    <a href="http://www.2012-cap.com">Wholesale Hats&Caps</a><br>
    <a href="http://www.2012-cap.com">New Era Fitted Hats</a><br>
    <a href="http://www.2012-cap.com/mlb-hats-c-3133.html">Cheap MLB Hats</a><br>
    <a href="http://www.2012-cap.com/nba-hats-c-3197.html</a><br>Cheap NBA Hats</a><br>
    <a href="http://www.2012-cap.com/monster-energy-hats-c-3237.html"></a><br>
    <a href="http://www.2012-cap.com/red-bull-hats-c-3293.html">Red Bull Hats</a><br>
    <a href="http://www.2012-cap.com/superman-hats-c-3300.html">Superman Hats</a><br>



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.