Changing how Bamboo upgrades the Subversion working copy version during checkout

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Bamboo automatically upgrades any Subversion source code working copy it checks out by running svn upgrade (more information here). If you use a Subversion client version other than the one that runs on Bamboo to access this code, any Bamboo builds on that code may fail. This KB provides you with configuration options to prevent that.


  • All Bamboo releases
  • Subversion repositories


Bamboo always applies the latest Subversion working copy version when checking out code and possibly pushing it back to the repository. If you want to tell Bamboo to use a specific Subversion working copy version, you will need to run Bamboo with the following system property:


where X.X is the SVN version that you want to retain for your code.
(info) Valid values for this parameter are 1.3, 1.4, 1.5, 1.6, 1.7, and 1.8

For example, setting this parameter to 1.5 tells Bamboo to:

  • Check out code to version 1.5 if no working copy exists, and
  • Do not automatically upgrade any already checked-out code of an existing working copy to be compatible with Subversion 1.6.

Please check the Configuring your system properties page to know how to add the -Dbamboo.svn.wc.format=X.X property to Bamboo.

Last modified on Oct 16, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.