Deploy Artifacts from Archive

JFrog REST APIs

Content Type
REST API
ft:sourceType
Paligo

Description: Deploys an archive containing multiple artifacts and extracts it at the specified destination maintaining the archive's file structure.

Deployment is performed in a single HTTP request and only the extracted content is deployed, not the archive file itself.

By default, deployment of artifacts is performed sequentially. However, from Artifactory 7.96.3 and later versions, deploying artifacts can also be performed in multiple parallel threads by means of the system parameter artifactory.explode. archive.threads. For example, if you set artifactory.explode. archive.threads = 10, the deployment of the artifacts contained in the archive will be performed in 10 parallel threads per archive file and this can save considerable time for large archive files.

Supported archive types are: zip; tar; tar.gz; and tgz. If the archive is omitted from the call, a response of "100 - Continue" is returned.

Note

  • Requires Artifactory Pro.

  • Deployment of compressed archives (unlike tar) may incur considerable CPU overhead.

Security: Requires a user with 'deploy' permissions (can be anonymous)

Usage: PUT path1/to/repo-key/ /path2/to/archive.zip

Headers: X-Explode-Archive: true - archive will be exploded upon deployment, X-Explode-Archive-Atomic: true - archive will be exploded in an atomic operation upon deployment.

Produces: text/plain

Since: 2.6.3

Sample Usage:

PUT /libs-release-local/ /Users/user/Desktop/archive.zip