Skip to end of metadata
Go to start of metadata

Overview

You can deploy artifacts into a local repository of Artifactory from the Artifacts module by clicking Deploy to display the Deploy dialog. Artifacts can be deployed individually or in multiples.

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, simply fill in the fields in the Deploy dialog and click "Deploy".

Deploying a single 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 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 Multiple Files

To deploy multiple files together, simple set the deploy Type to Multi, fill in the rest of the fields in the dialog and click "Deploy".


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