Overview

Artifactory offers UI 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 under Admin:Import & Export:Repositories

Deploying a Single Artifact

Single-artifact deployment is done from Deploy:Single Artifact.
Deployment is a two-step process:

1. In the first step you simply upload an artifact file to Artifactory.
2. After you've uploaded the file Artifactory will try to 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 will be 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 will make will be 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 don't have to follow the Maven repository layout convention, you can turn off the Deploy as Maven Artifact and edit the target deployment path manually.

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

Why was my deployment rejected? Deployment can fail for various reasons, as whole or partially. The most common reasons for 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 done from Deploy:Artifacts Bundle.
This is a very convenient feature for deploying multiple artifacts in one go.
Artifacts should be packaged in a zip archive and contained in the file structure that they should be deployed with. For example, the structure of the (partial) zip for Hibernate will look like this:

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 zip is a single step which ends with all zipped artifacts deployed into the selected repository.