Use the Subversion source configuration type (SCT) to load artifacts from Subversion. The Subversion SCT is implemented as an external type.
To use Subversion as an artifact source, select Subversion from the Source Config Type list and specify its properties. For details about creating components, see Create components.
Note: The Subversion source configuration type integration is not the same as the Subversion plugin. Plugins are special integrations used in processes. For details, see Subversion plugin.
Subversion SCT settings
The following table describes the properties specific to the Subversion source configuration type:
|Repository URL||Base URL for the Subversion repository.|
|Watch for tags||Watch for new tags instead of new versions.|
|Includes||The patterns to match files to include in the upload. The wildcard ** indicates every directory, and the wildcard * indicates every file. For example, the pattern dist/**/* retrieves the entire file tree under the dist directory.|
|Excludes||The patterns to match files to exclude from the upload.|
|Password||Password associated with the username.|
|SVN Path||Specify the path to the Subversion client executable. Enter the full path if necessary.|
|Preserve Execute Permissions||(Optional) Select this option to save file execute permissions along with the files.|
|Use Latest Component Properties for Version Download||
(Optional) Select this option if you want Deployment Automation to use the current component properties instead of the properties that are set when the version is created.
Note: Component version properties are always preserved when a version is created.
|Copy to CodeStation||
(Optional) Use this option to create a tamper-proof copy of the artifacts and store them in the DA's embedded repository, CodeStation.
For optimal use of Deployment Automation, we recommend that this option is selected.
Clear the option to save pointers to versions rather than the versions themselves. This way, you can track versions and save space on your Deployment Automation server, but this limits your ability to download individual versions.
For details on maintaining versions in external sources, see CodeStation: maintain versions externally.