Usage

When using a versioned file system, each subdirectory in the target directory is treated as a different version of the artifacts. You can set the server to check for new subdirectories periodically and automatically create component versions when new subdirectories are detected.

You need to define an HCL Launch component which defines the source and processes for the FileSystem repository. The component contains the information for importing the artifacts and any processes to implement on the artifacts.

To create a File System (Versioned) source configuration type of component arrange the artifacts inside a parent folder and subfolders based on the file system layout.

 myComponent/
    version n/
       files
    version n+1/
       files

For example, the following file structure shows a component with two versions and two files in each version. The two component versions are 1.0 and 2.0.

 myStaticWebContent/
    1.0/
      index.html
      logo.gif
    2.0/
      index.html
      logo.gif

To import artifacts with versions, create a directory with subdirectories that represent the versions of the artifacts. Then, create the component with the File System (Versioned) source configuration type.

After the component is created use the Components page in the user interface to import a version of the artifacts if automatic import was not selected.

Step palette

To access this plugin in the palette, click Source and Repositories > File System Versioned.

Create a component

To create a component, complete the following steps. For more information, see .

1. In the HCL user interface, click Components and then click Create Component.
2. In the Create Component window, specify a name and description for the component.
3. In the Teams fields, specify the access information for the new component.
4. To use a template for the new component, select a template from the Template list. In this case, the component inherits source configuration, properties, and processes from the template.
5. In the Source Config Type list, select File System (versioned).

   

6. Specify the properties for the component. See the Setting tab for descriptions.
7. Click Save.

Import a version

When the artifacts are imported, a component version is created using the version of the package. You can specify to import a specific package version or import all versions. If importing all versions, a component version is created for each version.

1. Click the Versions tab for the component.
2. Click Import New Versions.
3. Specify a specific version of the package to import, or leave blank to import the latest version of the package available in the repository. Additionally, enable Import All Versions to import all versions of a package.
4. Click Save.

Steps

The following process steps are available in the File System (Versioned) plugin.

• Import Version

Import Version

This step has no input properties.

Settings and Roles

The plugin adds these roles automatically to resources. You cannot add these roles manually.

• FileSystemVersionedComponentProperties

FileSystemVersionedComponentProperties