Deploy Artifacts from Archive

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

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

By default, the deployment of artifacts is performed sequentially. However, starting from Artifactory 7.96.3, artifact deployment can be performed in multiple parallel threads using 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, which can save considerable time for large archive files.

Supported archive types: zip, tar, tar.gz, tgz.

Note: Requires Artifactory Pro. Deployment of compressed archives (unlike tar) may incur considerable CPU overhead.

Since: 2.6.3

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

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length ≥ 1

Repository key

string
required
length ≥ 1

Path where the archive should be extracted (must end with archive filename)

Body Params

Binary content of the archive file (zip, tar, tar.gz, or tgz)

Headers
boolean
enum
required

Must be set to true to explode the archive upon deployment

Allowed:
boolean

If true, archive will be exploded in an atomic operation upon deployment

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
URL
LoadingLoading…
Response
Choose an example:
text/plain
application/json