The Subversion source configuration type is implemented as an external type.
Subversion (SVN) is an open source version control system.
To use Subversion as an artifact source, select Subversion from the Source Config Type drop-down list box and then configure the type-specific fields described here. For information about creating components, see Create components.
Note: The Subversion Source Config Type integration is not the same as the Subversion plugin. Plugins are special integrations used in processes. For details, see Subversion plugin.
Subversion Fields Table
|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
The patterns to match files to exclude from the upload.
|User||Subversion user name|
|Password||Password associated with the user name|
|SVN Path||Specify the path to the Subversion client executable. Enter the full path if necessary.|
|Preserve Execute Permissions||When enabled, file execute permissions are saved with the files.|
|Use Latest Component Properties for Version Download||
If this is selected, the current component properties are used to download this component's version artifacts in Versions > Artifacts. You should deselect this if the component's storage location or connection details have changed since the version artifacts you want to download were imported, so that the component properties that were set when the version was created are used instead. For more details on maintaining versions externally, see Import component versions.
|Copy to CodeStation||
This option, selected by default, creates a tamper-proof copy of the artifacts and stores them in the embedded artifact management system, CodeStation. For optimal use of Deployment Automation, the check box should be selected.
If you deselect Copy to Codestation for this source configuration type, pointers to versions are saved in Deployment Automation rather than the versions themselves. This enables you to track the versions, but limits some functionality in Deployment Automation. For more details on maintaining versions externally, see Import component versions.