Skip to end of metadata
Go to start of metadata
Table of Contents

Overview

Artifactory offers configuration-based deployments in two forms:

  1. Uploading and deploying a single artifact
  2. Uploading and deploying a bundle of artifacts

For deploying/importing whole repositories, you may want to use the Import Repository feature. Go to the Admin tab and then Import & Export -> Repositories

Deploying a Single Artifact

Single-artifact deployment is performed from the Deploy tab and then Deploy -> Single Artifact.

Deployment is a two-step process:

  1. Upload an artifact file to Artifactory.
  2. Make smart guesses about your artifact details (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.

Maven vs. Non-Maven Deployment

You can choose between Maven and non-Maven artifact deployment.

When deploying a Maven artifact you can edit the auto-filled GroupId, ArtifactId, Version, Classifier and Type details. The changes you make are auto-reflected in the target path displayed.  You can ask for automatic POM generation if one is missing in the target repository and you can even edit the POM manually (make sure you know what you are doing!).

For non-Maven artifacts, such as Ivy artifacts that do not have to follow the Maven repository layout convention, you can deactivate the Deploy as Maven Artifact and edit the target deployment path manually.

Once you are happy with the deployment details, mark the Deploy Artifact checkbox to deploy the artifact into Artifactory.

Why was my deployment rejected?

Deployment can fail for various reasons, as a whole or partially. 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.

Deploying a Bundle of Artifacts

Bundle deployment is performed from the Deploy tab and then Deploy -> Artifacts Bundle.

This is a very convenient feature for deploying multiple artifacts in one go.  The following archive extensions are supported: zip,tar,tar.gz,tgz

Artifacts should be packaged in an archive and contained in the file structure they should be deployed with. For example, the structure of the (partial) archive for Hibernate appears as follows:

org-
    hibernate-
              hibernate-
                        3.3.2GA-
                                hibernate-3.3.2.GA.pom
                                hibernate-3.3.2.GA.jar
              hibernate-entitymanager-
                                      3.3.2GA-
                                              hibernate-entitymanager-3.3.2.GA.pom
                                              hibernate-entitymanager-3.3.2.GA.jar

Uploading and deploying the archives is a single step ending with all archived artifacts deployed into the selected repository.

  • No labels