Page tree
Skip to end of metadata
Go to start of metadata


You can deploy artifacts into a local repository of Artifactory individually or as a bundle.

Using Import to "deploy" a whole repository

If you want to "deploy" a whole repository, you should actually import it using the Import Repository feature in the Admin tab under Import & Export | Repositories.

Page Contents

Deploying a Single Artifact

To deploy a single artifact, in the Deploy tab select Deploy | Single Artifact

This is a two-step process:

  1. Select Choose file to browse for the artifact you want to upload.
    Uploading a single artifact to deploy
  2. Set your Target Path and click Deploy Artifact. If you are deploying a Maven artifact, you may need to configure additional attributes as described in the next section.

Suggested Target Path

Artifactory will suggest a Target Path based on the details of your artifact (this works for both Maven and Ivy). For example, if a JAR artifact has an embedded POM under its internal META-INF directory, this information is used.

Deploying Maven Artifacts

If you are deploying an artifact that conforms to the Maven repository layout, you should set Deploy as Maven Artifact to expose fields that specify the corresponding  Maven attributes - GoupIDArtifactIDVersion, Classifier and Type.

The fields are automatically filled in according to the artifact name, however you can edit them and your changes will also be reflected in the Target Path.

If your target repository does not include a POM, set Also Deploy Jar's Internal POM/Generate Default POM, to use the POM within the artifact you are deploying, or generate a default POM respectively.

You may also use the POM Editor to manually edit the POM if you need to modify the artifact coordinates, or remove unwanted repository references.

Take care when editing the POM manually

If you are editing the POM manually, be very careful to keep it in a valid state.

Deploying a Maven Artifact

Deploying with Properties

Properties can be attached to the uploaded file by specifying them on the Target Path.

First, unset the Deploy as Maven Artifact check box, if necessary.

Then, in the TargetPath field, add the properties delimited from the path and from each other by semicolons. Each property is a key=value pair.

For example, to upload an artifact with the property qa set to "passed", and build.number set to "102", use the following Target Path:


Deploying an Artifact Bundle

An artifact bundle is deployed as a set of artifacts packaged in an archive with one of the following supported extensions: zip, tar, tar.gz, tgz.

File structure within the archive

Artifacts should be packaged within the archive in the same file structure with which they should be deployed to the target repository.

To deploy an artifact bundle, in the Deploy tab select Deploy |  Artifacts Bundle.

Then select Choose file to upload the archive containing the artifacts to deploy, select the Target Local Repository and select Deploy.

Deploying an Artifact Bundle

Failed Uploads

The most common reasons for a rejected deployment are:

  • Lack of permissions
  • A conflict with the target repository's includes/excludes patterns
  • A conflict with the target repository's snapshots/releases handling policy.


  • No labels