Clone Release Libraries

Similar to Clone Organization Library, there are several reasons to manage Release Libraries outside the project. So, the Maestro Offline Build (MOB) tool provides functionality to clone release libraries separately.

The user must be assigned a Role with the permission to clone release libraries:

• Scm Release Library View

Synopsis

maestro release-clone [ options ]

Options

All options are optional unless otherwise indicated.

info

Both short and long options are shown in the table below. When specifying a command, use either a short option or long option but not both.

Option	Description
-s --server	Server (Required) The URL of the maestro server.
-u --user	Username (Required) The username of a Maestro user that has the required permissions.
-p --password	Password (Required) The password for the user specified in the Username option.
-n --release-version	Release Version (Required) The SCM Project path for the project being cloned.
-l --local-path	Local Path The path on the local file system to place the files. If not provided, files are exported to the current working folder.
-f --force-overwrite	(Flag) Force Overwrite Indicate that any existing contents in the output folder may be overwritten. If not specified and the folder is not empty, an error is displayed.

Examples

• Clone the 20.05.0 release to the current folder.

  maestro release-clone -s https://maestro.avoka.com.au -u username -p p@ssw0rd -n 20.05.0

• Clone the 19.05.5 release to a specified folder.

  maestro release-clone -s https://maestro.avoka.com.au -u username -p p@ssw0rd -n 19.05.5 -l c:\releases\19.05.5