FlexDeploy - Subversion Plugin Guide

Created by Copy Page Tree
Last updated: Feb 10, 2017 by Karl Henselin

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

  • 1.7+

Key Features

  • Easily configured
  • No installation necessary
  • Executes commands using embedded Java API, so SVN client necessary.

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

Required

Description

Subversion URL

FDSVN_URL

Yes

Base Subversion repository URL.

Error rendering macro 'excerpt-include' : No link could be created for 'FlexDeploy 4.0 Documentation'.

Subversion User

FDSVN_USER

Yes

The user name for connecting to Subversion. User name must have read write access, if you plan to perform tag operations.

Subversion Password

FDSVN_PASSWORD

Yes

The password for the FDSVN_USER.

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.

Plugin Operations