Artifactory - Upload Artifacts

Methods to Upload Artifacts

Uploading artifacts to Artifactory involves storing your build outputs, libraries, or other files within one of Artifactory’s repositories.

Here’s how to upload artifacts in Artifactory and some tips on how to use the functionality efficiently:

Web UI Upload

• Slow Performance: It takes a significant amount of time compared to programmatic methods.

• Timeout Failures: Uploads frequently fail based on platform-configured network timeouts (e.g., nginx, Zscaler, etc.).

• Unreliability: The UI connection is generally not reliable for consistent artifact delivery.

• Size Limitations: UI uploads are strictly limited in size (platform dependent). Expected Solution: To avoid these issues, we highly recommend using the JFrog CLI or REST API (cURL) commands explained below. These are the recommended, robust solutions to upload or download artifacts safely and efficiently.

Step-by-Step Process :

1. Log in to the Artifactory Web UI.
2. Navigate to the relevant local repository where you want to store your artifact (e.g., private-maven-test-local).
3. Select the Deploy button.
4. Either drag and drop the artifact into the provided upload area or use the Browse button to select the file from your system.
5. Configure the target path within the repository.
6. Select Deploy to upload the artifact.

This method should be used for exceptional cases; always prefer programmatic ways (cURL / JFrog CLI).

REST API Upload (cURL)

You can automate and manage your repository efficiently without the UI limitations with the REST API. You can discover all available endpoints in the official REST API guide.

Endpoint: PUT /artifactory/{repoKey}/{filePath}

• Construct the upload URL using your repository key and desired file path.

• Use a command-line tool like curl or integrate it within a script to upload:

  curl -H "X-JFrog-Art-Api:<api_key>" -T <file> "http://<artifactory_url>/artifactory/<repoKey>/<filePath>"
  

• Execute the command to upload the artifact.

Advantages: Highly reliable, bypasses UI timeout limitations, suitable for automation, can handle multiple or batch uploads, and integrates well with CI/CD pipelines.

Artifactory CLI (JFrog CLI)

The JFrog CLI is the most robust replacement for UI uploads, specially designed to handle large files and network interruptions gracefully.

• Installation: Download and install the JFrog CLI .

• Configuration:

  jfrog rt config
  

• Upload Command:

  jfrog rt u "<local_file_path>" "<repository_path>"
  

Uploading to a Specific Project (JFrog CLI):

To upload an artifact and explicitly assign it to a target project, use the --project flag followed by your Project Key:

jfrog rt u "<local_file_path>" "<repository_path>" --project "<project_key>"

Advantages: Simplifies interactions with Artifactory, natively supports bulk uploads, handles large artifact sizes reliably without UI timeout drops, and integrates well with automation scripts.

Build Tools Integration

Various build tools can integrate with Artifactory to manage and upload artifacts:

• Maven:
  • Configure Artifactory as a distribution repository in your pom.xml.
  • Deploy artifacts using the mvn deploy command.
• Gradle:
  • Set up Artifactory credentials and repository in your build.gradle.
  • Use the gradle publish task to upload artifacts.
• npm:
  • Configure Artifactory registry in .npmrc.
  • Use npm publish to upload the package.
• Docker:
  • Tag your Docker image with the Artifactory repository URL.
  • Use docker push to upload the image.

NextGen CICD

NextGen CICD is a modern approach to continuous integration and continuous delivery.

You can find more information on the Artifactory NextGen CICD . You can also find various exemples for Python or Java of using the NextGen CICD with Artifactory.

Tips for Efficiently Using Artifactory Uploads

1. Efficient Use of Repositories:

   • Organize artifacts logically within repositories (e.g., separate snapshots from releases). This helps in managing versioning and access controls efficiently.

2. Use Checksums:

   • Artifactory’s checksum-based storage prevents redundant uploads and saves storage space. Make sure to use checksum verification when uploading artifacts through API or CLI.

3. Bulk Uploads:

   • For large numbers of files or large artifacts, use the JFrog CLI or REST API to script bulk uploads. This ensures efficiency and decreases the risk of manual errors and network drops.

4. Repository Metadata:

   • Use metadata and properties during uploads to tag artifacts with relevant information (e.g., build number, environment). This enhances traceability and searchability.

5. Access Controls:

   • Set appropriate permissions and visibility for repositories to ensure that only authorized personnel can upload/modify the artifacts.

Troubleshooting Tips

• Authentication Issues: Failure to authenticate or permission denied errors.

• Connectivity Problems: Timeouts, network errors, or inability to reach the Artifactory server.

• Repository Configuration: Errors indicating the repository does not exist or is misconfigured.

• File Size and Limit: Uploads fail due to file size limits or storage quota issues.

• Artifact Checksum Validation: Errors due to checksum mismatch or verification failures.

• Others errors in CLI or inconsistent upload behavior.