File System (Basic) SCT

Use the File System (Basic) source configuration type (SCT) to import the contents of a specified directory from the file system.

File System (Basic) SCT overview

The File System (Basic) SCT is implemented as an external type.

When you use File System (Basic), Deployment Automation imports all contents of a designated directory from the file system as follows:

  • At import, imports everything in the given base path, including all files at the base path level, its subdirectories, and all files in all of its subdirectories.
  • If you specify the Version Name Pattern and Next Version Number, Deployment Automation auto-increments version numbers and assigns them as the component version names. With this option, you can use Import Versions Automatically or import manually.
  • If you do not specify a version name pattern, you must manually import the component version, and you need to specify a version name at the time of manual import. The Import Versions Automatically option, if selected, is ignored.

To use this SCT, select File System (Basic) as the Source Config Type when you create a component or component template. For details, see Create components.

Back to top

File System (Basic) SCT settings

The following table describes the settings specific to the File System (Basic) source configuration type.

Field Description
Base Path Base path for artifact storage.
Always Use Name Pattern When selected, the Version Name Pattern is used for new version names at the time of import. If this is not selected, the user is prompted for the version name at the time of import.
Version Name Pattern An optional field to create a template for automatic version names. Use ${version} to reference the Next Version Number field.
Next Version Number An integer used for the next version created. This number is automatically incremented for every version created.
Preserve Execute Permissions (Optional) Select this option to save file execute permissions along with the files.
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.

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.

Back to top

See also: