- 14 May 2021
- 1 Minute to read
- Updated on 14 May 2021
- 1 Minute to read
This is generated from the built in components of BuildMaster 7.0.0, and may be different than what you have installed (especially if you have extensions); go to [User Icon] -> Documentation within your BuildMaster instance to see exactly what operations are available.
Retrieves the specified artifact from the artifact library and deploys it to a directory.
Deploy-Artifact( Name: <text>, [To: <text>], [Application: <text>], [Release: <text>], [Build: <text>], [Deployable: <text>], [DeployAsZipFile: <true/false>], [TransferAll: <true/false>], [DoNotClearTarget: <true/false>], [Verbose: <true/false>], [OverwriteReadOnly: <true/false>], [OptimizedFileTransfer: <true/false>] );
This operation may be prefixed with
Core::, although this is a built-in namespace and isn't really necessary.
|Name||Format||Script Usage||Usage Notes|
|☆ Artifact name (default)|
|This argument is required.|
|Valid values are specific build numbers, or "furthest" or "latest".|
|Deploy as zip|
|Transfer all files|
|By default, files will only be transferred if the last modified date or file size has changed. If set to true, all files will be transferred regardless if they have been modified.|
This value should generally be set to false, except when it would take more time to compare the files than simply transferring and overwriting them all (i.e. the artifact contains thousands of small files).
|Do not clear target|
|Overwrite read-only files|
|Use optimized file transfer|
|Transfers artifact files using a new implementation that increases performance. This feature is still experimental, so verify results before using in production. This option is ignored if TransferAllFiles is true.|
Note: Specifying "latest" as the source package number will attempt to retrieve the artifact from the most recently created build, whereas "furthest" will use the one that has been deployed to the furthest environment in the pipeline.
Was this article helpful?