Working with the RM Repo

The RM repo (or CDA artifact source) is a built-in Artifact Source of type "internal repo" that allows you to consolidate Artifacts by providing you with better control, traceability and visibility.

For more information, see: Consolidating Artifacts in CDA with the RM Repository

This page includes the following:

Uploading Artifact Files to an Artifact

Important! This action can only be executed with the RM Repo Artifact Source. For more information, see: Consolidating Artifacts in CDA with the RM Repository

  1. Open the Release Automation perspective.
  2. Click the Applications tab.
  3. Double-click a Component to open it.
  4. Click the Artifacts tab. The list of Artifacts that are defined for the current Component is displayed.
  5. Double-click an Artifact to open it.
  6. Click the Upload button.
  7. Select the files/directory to upload.
  8. Select the Unpack archived files checkbox if you want to automatically unpack the files stored in one of the following formats: zip,tar,tar.gz
  9. Confirm the action.

    Notes:

    • The uploaded files are renamed to their checksum values. CDA uses checksums to identify the correct artifact content to be deployed. The file names are converted to their original values once they have been deployed to the Targets.
    • While uploading Artifact files, the metadata properties (Filename, Filepath, Timestamps, Checksum, File permission) will be automatically extracted and displayed in the Metadata field on ArtifactFiles entities.
    • You can manually upload additional file metadata (for example, timestamps) via REST See: REST API Reference. The Artifact Loader tool will only extract and store the values that have not been defined manually.

Artifact Loader

You can upload an artifact directory to the RM Repo with the Artifact Loader tool. To download the tool, navigate to the Artifact Sources view and click the Get Artifact Loader button.

Notes:

  • If you do not pass a specific path in the parameters, the current directory will be used. In that case, the .jar file stored in the directory will not be uploaded.
  • The artifact loader tool allows you to automatically unpack artifact zip files when deploying an artifact from the RM repo to the Targets. The zip content will be extracted into the same location.

Commands

  • Upload

    Parameters:

    • -a, --artifact

      Artifact name.

    • -p, --path

      Path to an absolute directory or file.

      Note: Add an asterisk at the end of the path to upload only the content files without the root folder. Example: --path "C:\Artifact\12.5.0*

    • -as, --artifact-source

      Name of the Artifact Source where the Artifacts are stored.

    • -url, --url

      URL of the CDA instance.

    • -u, --user

      User name.

    • -pwd, --password

      User password.

    • -f, --folder

      The folder of artifact. If the folder is not specified, the folder of the Artifact Source will be used as default.

    • -l2f, --log2file

      Writes the log to a log.txt file.

    • -i, --includes

      Source include rule (Ant-style path pattern matching).

    • -e, --excludes

      Source exclude rule (Ant-style path pattern matching).

    • -un, --unpack

      The archive types used to unpack the artifact. The types may be separated by a comma.

      Options: zip, tar or tar.gz

    • -cs, --case-sensitive

      Flag to indicate if the artifact upload is case-sensitive or not.

      Default: false.

    • -h, --help

      Display help message.

Example

java -jar artifact-loader-cli.jar upload --path C:\temp\document.txt --artifact 1.0.0 --artifact-source RM-Repo --url localhost/CDA --user 100/AUTOMIC/AUTOMIC --password ***

Upload Artifact Action in Component Workflows

The UploadArtifact Action uploads the Artifacts from the temporary CDA server to the RM Repo.

Notes:

  • The deployment of Artifacts in CDA will be only triggered after the artifact files have been fully uploaded to the RM Repo (Artifact status: uploaded). For more information, see: CDA Internal Artifact Source
  • To optimize the disk space, the Artifact files in the Temp folders (for example: Automic\Release.Manager\WebUI\StateFiles\ArtifactFiles) are deleted after the upload process has been completed (regardless of the state).

Downloading Artifact Files

Important! This action can only be executed with the RM Repo Artifact Source. For more information, see: Consolidating Artifacts in CDA with the RM Repository

You can download artifact files and folders to access the content of deployment Artifacts.

  1. Open the Release Automation perspective.
  2. Click the Applications tab.
  3. Double-click a Component to open it.
  4. Click the Artifacts tab. The list of Artifacts that are defined for the current Component is displayed.
  5. Double-click an Artifact to open it.
  6. Click the Download button in the toolbar to generate a .zip file containing the artifact files/folders. You will get notified when the requested zip file is ready.

Notes:

  • Downloading big artifacts files might require to increase the default timeout value defined in the web.config file. For more information, see: Configuring HTTPs Endpoints for CDA
  • You can also download one or more Artifact Files from the Artifact Files view of an Application Installation. See: Application Installations