Overview
Subversion
is an open source SCM designed as a compelling replacement to CVS. Subversion support in pulse™ uses a pure Java subversion client and thus has no external dependencies.
Configuration
url
Specifies the URL of the subversion repository you would like to check out from, including the protocol to use, the location of the server and path of the code line within the server. The URL given should be in the exact form used for the checkout command of the command line client svn.
Examples
To checkout the Jakarta ORO source over HTTP:
To checkout the trunk of "my-project" from server "svn.example.com" using svn over ssh:
username
Specifies the username to use to connect to the subversion server. The user must have access to the URL specified below.
This field is not required.
password
If the user configured above requires a password for authentication, it should be supplied in this field.
This field is not required, and need not be specified when using anonymous access or other authentication methods.
private key file
If using ssh private key authentication, the absolute path to the private key file on the pulse™ host machine.
This field is not required.
Examples
To use a private key generated for a dedicated pulse™ user on a Linux host:
key file passphrase
If using an ssh key file that has been encrypted with a passphrase, specify that passphrase using this field.
This field is not required, and is not used unless key file is set.
external monitor paths
Pulse includes some support for monitoring svn:externals references, as long as those references point into the same Subversion repository. To enable this support, you should set this field to a list of paths to check the svn:externals property for. These paths are relative to the Subversion URL specified above (to refer to the base of the checkout, use "."). When this field is set, pulse™ will monitor not only the URL specified above, but also any URLs referenced in the svn:externals properties of the paths listed in this field. Note that only URLs referring to the same Subversion repository are supported. Additionally, when checking out or updating source to a fixed revision (the normal case for a build), pulse™ will force code from the externals to the revision by a subsequent update in each external working copy.
verify externals
If using svn:externals support (see above), only externals from the same Subversion repository are supported. By default this is verified by pulse™. However, as this may take significant time, you may wish to disable verification by unchecking this option.
monitor
The monitor field defines whether or not the configured SCM will be monitored for changes. By default, this value is set to true.
