Deploy Artifacts

JFrog Artifactory Documentation
Products
JFrog Artifactory
Content Type
User Guide

In the JFrog Artifactory UI, you can deploy artifacts to JFrog Artifactory one at a time or in batches. You can also upload an archive file as a bundle and Artifactory will expand the file contents on deployment.

Artifactory repositories have built-in logic for parsing metadata, creating index files, and optimizing performance by package type. Uploading non-conformant content like images, text files, and other resources that are not wrapped in a package format, can impact indexing and reduce performance. Make sure to deploy generic or non-conformant content to a Generic repository type.

Note

The Artifactory UI supports uploads of up to 100MB. To deploy artifacts larger than 100MB, use the JFrog CLI, a package manager client, or a multi-part upload.

Prerequisites: Make sure your artifact name adheres to naming conventions. For more information, see Artifact Naming Conventions.

To deploy artifacts:

  1. On the Platform module, navigate to Artifactory > Artifacts. The artifact browser appears.

  2. Click the action menu and select Deploy (Upload). The Deploy window appears.

  3. From the Target Repository menu, select the repository where you want to deploy artifacts.

  4. Select one of the following tabs:

    • Single Deploy: Upload one artifact to the target repository. This is the default option.

    • Multiple Deploy: Upload more than one artifact to the target repository.

  5. Drop or select the files you want to upload.

    deploy_bundle_layout.png

  6. Optionally, in the Target Path field, enter a custom path in the target repository or add artifact properties using matrix parameters. For more information, see Using Properties in Deployment and Resolution.

  7. Depending on the file type, optionally select any of the following checkboxes:

    • Deploy According to Layout: Select this option to deploy the package according to the configured layout that appears in the Target Repository section. When selected, the layout tokens are exposed for configuration. Changes are reflected in the target path.

      deploy_according_to_layout.png

    • Deploy as Bundle Artifact: Select this option when you upload multiple artifacts packaged into a .zip, .tar, tar.gz, or .tgz archive file. Artifactory extracts the archive contents when you deploy it.

      Note

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

    • Deploy as Maven Artifact: For Maven artifacts, this option lets you configure Maven artifact attributes like GroupID, Version, Classifier, and Type. The attributes are automatically populated according to the artifact name. You can edit them and changes are reflected in the target path.

    • Generate Default POM / Deploy Jar's Internal POM: For Maven artifacts, select this option to use the POM within the artifact you are deploying or generate a default POM. Use this option if your target repository does not include a POM.

      Note

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

  8. Click Deploy.

Artifact Naming Conventions

The following conventions and limitations apply to artifact names when deploying from the JFrog Artifactory UI:

  • Do not use the special characters |, *, ?, or ".

  • You can use & as part of an artifact name, but not as a path token.

  • A spaces before / is not allowed.

Troubleshooting Failed Deployment

The following are some of the most common reasons for failed deployments:

  • Inadequate permissions

  • Conflict with target repository include/exclude patterns

  • Conflict with target repository snapshots/releases handling policy

Related Topics