Changing automatic upgrades of working copies from Subversion

The SVNKit library in Bamboo was upgraded to version 1.2, in Bamboo 2.1.4.

This has two implications for source code checked out by Bamboo:

• any source code checked out by Bamboo will be automatically upgraded to be compatible with Subversion 1.5.
• (Bamboo 2.1.4 and earlier) any working copies already checked out are automatically upgraded to be compatible with Subversion 1.5.

This does not adversely affect any pre-1.5 Subversion servers. However, if you use a pre-1.5 Subversion client to access code checked out by Bamboo, then any Bamboo builds on that code may fail. Please refer to BAM-3241 for further details.

You can configure Bamboo to prevent it from automatically upgrading any source code checked out, by configuring the following parameter:
bamboo.svn.compatibility.14
This parameter is only available from Bamboo 2.1.5 onwards.

Setting this parameter to true tells Bamboo to

• check out code to version 1.4 if no working copy exists
• not to automatically upgrade any already checked out code of an existing working copy to be compatible with Subversion 1.5.

To change this parameter for your Bamboo instance, you can follow either one of the methods below:

• Add the parameter with a '-D' prefix and appropriate value, in your command line when starting Bamboo. e.g. -Dbamboo.svn.compatibility.14=true, or
• Add the parameter as a property in your <bamboo-home>/bamboo.cfg.xml file.
  e.g. <property name="bamboo.svn.compatibility.14">true</property>