Skip to main content
The FlexDeploy Subversion plugin makes it easy to interact with source code stored in the Subversion SCM. There is no need to install an SVN client. The plugin uses a Java based API to interact with Subversion. FlexDeploy allows users to configure Subversion repository connection details in instances which are shared by various projects. The project specific configuration is stored separately in the projects which allows for easy export and tag operations during workflow executions.
  • Create an SCM Instance for Subversion and define the URL, User and Password information. You can also validate the connection when creating SCM Instances.
  • Inside of your projects, select Subversion as SCM Type, select the instance that you created, and provide details like Trunk, Branch, Tag Path etc. which are defined as Groovy scripts. The connection there will bring across your repository URL, username, password and authentication methods.

​
Supported Versions

  • SVN Repositories version 1.7+
  • Java 8 is required to use this plugin

​
Key Features

  • No installation necessary
  • Ability to connect using svn+ssh with private key, http, or https
  • Executes commands using embedded Java API, so no SVN client is necessary.

​
Integration Instance Properties

FlexDeploy supports creation of SCM instances, and the following properties will be configured for each SVN Instance. These properties are available to all operations.

Property Name

Property Code

Required

Description

Subversion URL

FDSVN_URL

Yes

Base Subversion repository URL. 

When connecting with svn+ssh the URL needs to follow a certain format svn+ssh://<SVN_HOSTNAME>/<ABSOLUTE_PATH_ON_SERVER_TO_REPO>

Examples:

Subversion User

FDSVN_USER

Yes

The username for connecting to Subversion. Username must have read write access, if you plan to perform tag operations.

Subversion Password

FDSVN_PASSWORD

Yes

The password for the FDSVN_USER.

SSH Private Key

FDSVN_PRIVATE_KEY

Yes

The private key file path for use with SSH. Passphrase for private key is not supported.

Private key is generally in .ssh folder of user, which can be flexdeploy application process user or endpoint user (for plugin execution). Location must be same (different key is fine but just with same name and location).

If necessary, you can generate key using (ssh-keygen -t rsa) and put public key in target user’s authorized_keys file, which should be in $HOME/.ssh folder.

Subversion Authentication Methods

FDSVN_AUTH_METHODS

No

One or more SVN authentication methods. For example: Basic, Digest, Negotiate, NTLM (Optional). 
You can specify one or more methods as necessary. For example: if you are using “Windows Authentication” with Visual SVN and only “Integrated Windows Authentication” is supported, use NTLM.

Subversion Commit URL

FDSVN_COMMIT_URL

No

Configure this property if URLs automatically generated by FlexDeploy does not meet your needs.

Available variable(s):

  • {COMMIT} - subversion revision number like 10, 15, etc.

e.g. https://repo.mydomain.com/MyOrg/FD-REPO/commit/\{COMMIT\}

Available supported since 9.0.0.7.

Subversion File URL

FDSVN_FILE_CONTENT_URL

No

Configure this property if URLs automatically generated by FlexDeploy does not meet your needs.

Available variable(s):

  • {PATH} - This will be either Trunk Path Script (used for main branch) or Branch Path Script (for all branches other than main) e.g.: /trunk/HumanResources/Project1

  • {FILEPATH} - Path of the file as discovered from SCM, e.g. /sql/EmployeeData.sql

e.g. https://repo.mydomain.com/MyOrg/FD-REPO/blob/\{PATH\}/\{FILEPATH\}

Available supported since 9.0.0.7.

Subversion File Commit URL

FDSVN_FILE_CONTENT_COMMIT_URL

No

Configure this property if URLs automatically generated by FlexDeploy does not meet your needs.

Available variable(s):

  • {COMMIT} - subversion revision number like 10, 15, etc.

  • {PATH} - This will be either Trunk Path Script (used for main branch) or Branch Path Script (for all branches other than main) e.g.: /trunk/HumanResources/Project1

  • {FILEPATH} - Path of the file as discovered from SCM, e.g. /sql/EmployeeData.sql

e.g. https://repo.mydomain.com/MyOrg/\{PATH\}/\{FILEPATH\}/commit/\{COMMIT\}

Available supported since 9.0.0.7.

​
Plugin Operations