File System (Versioned)
The File System (Versioned) source configuration type is implemented as an external type.
When you select File System (Versioned) for Source Config Type, Deployment Automation imports the subdirectories of a designated directory from the file system as follows:
- At import, imports only the subdirectories and contents of subdirectories; it does not include the contents directly in the base path.
- The first level subdirectory in the base path becomes a component version and the version name is the name of the subdirectory.
- It does not prompt for version name during manual import; version naming is always automatic and is always the first subdirectory name.
File System (Versioned) Source Fields Table
|Base Path||Path to directory containing artifacts. The content of each subdirectory within the base directory is considered a distinct component version. The subdirectory with the most recent time-stamp is considered the "latest version"; however, is a good practice to name the subdirectories according to your version scheme, such as v1.0, v1.1, and so on.|
|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. See Maintaining Versions Externally.
|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. See Maintaining Versions Externally.