DA VFS plugin

Deployment Automation Versioned File Storage (VFS) enables you to add artifacts to the Deployment Automation version repository CodeStation. With the DA VFS plugin, you can access artifacts in CodeStation.

To use the plugin's steps, open your process and navigate to Repositories > Artifact > DA in the Tools pane.

In this topic:

Download Artifacts step

Use the Download Artifacts step to download artifacts from a versioned file storage. In the standard plugin, this storage is CodeStation.

The following table describes the step's properties:

Property	Description
Directory Offset	The working directory to be used when running the step, relative to the current working directory.
Includes	The list of the files relative to the directory offset that you want to include in the selection. You can use wildcards. 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	(Optional) The list of the files relative to the directory offset that you want to exclude from the selection. You can use wildcards. The wildcard ** indicates every directory, and the wildcard * indicates every file.
Sync Mode	(Optional) Select the sync mode: None. Do not use a sync mode. Sync (default). Transfer only changed files, removing files that exist only in the previously-deployed version. Sync and Clean. Remove all files not contained in the currently deployed version.
Full Verification	(Optional) Valid only when Sync Mode is set to Sync or Sync and Clean. If this option is selected, hashes are computed on each file in the destination artifact set to determine whether network transfer is necessary. Otherwise, files are compared by date modified and size.
Set File Execute Bits	(Optional) Select this option to set the file execute bits on the files which have them set in the repository.
Verify File Integrity	(Optional) If this option is selected, the download process verifies that the downloaded files match their hash. Selecting this may negatively impact performance.

Back to top

Upload Artifacts step

Use the Upload Artifacts step to upload artifacts to a versioned file storage. In the standard plugin, this storage is CodeStation.

The following table describes the step's properties:

Property	Description
User	The name of the user making the change.
Comment	A comment that describes the change.
Directory Offset	The working directory to be used when executing this command. This is relative to the current working directory.
Includes	The list of the files relative to the directory offset that you want to include in the selection. You can use wildcards. 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.
Update	(Optional) If this option is selected, the change set is added to the old one rather than creating a completely new one.
Excludes	(Optional) The list of the files relative to the directory offset that you want to exclude from the selection. You can use wildcards. For multiple file paths, specify each path on a new line.
Save File Execute Bits	(Optional) If this option is selected, the file execute bits are saved with the files.

Back to top

Upload Step Attachment step

Use the Upload Step Attachment Artifacts step to upload a designated step attachment to the Deployment Automation server.

The following table describes the step's properties:

Property	Description
Attachment Name	Name of the file attachment to upload.
Path	The path to the file attachment you want to upload. The default property for the path is ${p:prevStep/logPath}, which uploads the log of the previously run step and attaches it to this step. For details on properties, see Built-in properties.
Target Step	The target step to which the attachment should be uploaded.
Format	(Optional) The format of the attachment file. Select from the following options: Plain Text HTML Image Binary
Delete After Upload	(Optional) If this option is selected, the file attachment is deleted after it is uploaded to the remote server.

Back to top

Verify Local Artifacts step

Use the Verify Local Artifacts step to compare artifacts on a local machine with the inventory in a versioned file storage. In the standard plugin, this storage is CodeStation.

The following table describes the step's properties:

Property	Description
Directory Offset	The working directory to be used when executing this command. This is relative to the current working directory.
Includes	The list of the files relative to the offset directory that you want to include in the selection. You can use wildcards. 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	(Optional) The list of the files relative to the offset directory that you want to exclude from the selection. You can use wildcards.

Back to top

See also:

• Create plugins
• Load and upgrade plugins