Back to CMS Configuration

Subversion

Stages supports SVN 1.9, 1.10 and 1.14

Example Configuration

<cms-type name="subversion">
    <!-- Global Properties -->
    <cms-host ident="subversion.example.ident" name="https://subversion.example.net:1234" displayName="Subversion Example Server">
        <!-- Host Properties -->
        <cms-property name="user" value="subversion_username" />
        <cms-property name="password" value="subversion_password" />
    </cms-host>
</cms-type>

Host Properties

These configuration properties affect the behavior of one Subversion server.

* Required
Properties marked with * are required for the adapter to work.

# Required but can also be set in web-application
Properties marked with # are required but can also be set in the File Management section in the Stages web-application as well. The value entered in the web-application overrides the one from the config.xml.

+ Required but with default
Properties marked with + are required, but there is a default value. This values can be overridden by configuring it in the config.xml.

user #

The Subversion user needs read and write access to the repository.

password #

> http.connection.timeout +

> http.max.connections +

> http.ssl.allow.all +

> use.system.account.for.download +

> domain

> http.authentication.hostname (required for ntlm authentication)

Repository Configuration

Access to Subversion projects can be configured in Stages processes via “Management > File Management > Repositories”.

Name: The name of this Subversion configuration. This name will be used by Stages to refer to this repository configuration (e.g. in repository plan)
Subversion Server: This selection field contains an entry for each cms-host section in the Stages configuration file (config.xml). You can select the host for this repository configuration.
Repository Path Define the path to the Subversion repository. This overwrites the path from the URL entered in the configuration file (config.xml).

Example:

Enforce Usage of System Account If this is set to true, Stages will use the user credentials from this repository configuration for ALL operations. This means, every check-in, download or lock operation will be executed with the same username.
Username: Define a username for this repository configuration. This overwrites the property username from the configuration file (config.xml).
Password Define a username for this repository configuration. This overwrites the property password from the configuration file (config.xml).
Default Lifecycle Select a lifecycle from the process metamodel as default for files from this repository.

Known Limitations

svn:needs-lock is actually not supported by Stages

If the svn attribute “svn:needs-lock” is set for a file this will be ignored by Stages