Artifactory 5.x

Using Artifactory 6.x ?
JFrog Artifactory 6.x User Guide

Expand all   Collapse all

Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata

Overview

To configure a remote repository, in the Admin module, go to Repositories | Remote and click it to display the Edit Repository screen.

Common Basic Settings

The following are fully described in the Common Settings page.

Additional Basic Settings

URL
The URL for the remote repository. Currently only HTTP and HTTPS URLs are supported.
Offline

If set, this repository will be considered offline and no attempts will be made to fetch artifacts from it.

For more details, please refer to Single Repository Offline below. 

Page Contents

Read More

 

Type-Specific Basic Settings

Repositories may have additional Basic settings depending on the Package Type.

Maven, Gradle, Ivy and SBT Repositories

Remote Maven Repository Settings

Checksum Policy

Checking the Checksum effectively verifies the integrity of a deployed resource. The Checksum Policy determines how Artifactory behaves when a client checksum for a remote resource is missing or conflicts with the locally calculated checksum.

There are four options:

  1. Generate if absent (default): Artifactory attempts to retrieve the remote checksum, If it is not found, Artifactory will automatically generate one and fetch the artifact. 
    If the remote checksum does not match the locally calculated checksum, the artifact will not be cached and the download will fail.
  2. Fail: If the remote checksum does not mach the locally calculated checksum, or is not found, the artifact will not be cached and the download will fail.  
  3. Ignore and generate: Artifactory ignores the remote checksum and only uses the locally generated one. As a result, remote artifact retrieval never fails, however integrity of the retrieved artifact may be compromised.
  4. Ignore and Pass-thru: Artifactory stores and passes through all remote checksums (even if they do not match the locally generated one). If a remote checksum is not found, Artifactory generates one locally. As a result, remote resource retrieval never fails, however integrity of the retrieved artifact may be compromised, and client side checksum validation (as performed by Maven, for example) will fail.
Max Unique Snapshots
Please refer to Max Unique Snapshots under Local Repositories.
Eagerly Fetch Jars
When set, if a POM is requested, Artifactory attempts to fetch the corresponding jar in the background. This will accelerate first access time to the jar when it is subsequently requested.
Suppress POM Consistency
By default, Artifactory keeps your repositories healthy by refusing POMs with incorrect coordinates (path). If the groupId:artifactId:version information inside the POM does not match the deployed path, Artifactory rejects the deployment with a "409 Conflict" error.

You can disable this behavior by setting the Suppress POM Consistency checkbox.

Eagerly Fetch Sources
When set, if a binaries jar is requested, Artifactory attempts to fetch the corresponding source jar in the background. This will accelerate first access time to the source jar when it is subsequently requested.
Handle Releases
Please refer to Handle Releases under Local Repositories.
Handle Snapshots
Please refer to Handle Snapshots under Local Repositories.

Other Repository Types

For other type-specific repository configuration, please refer to the specific repository page under Artifactory Pro.

Handling Offline Scenarios

Artifactory supports offline repository management at two levels:

  • Single Repository: One or more specific remote repositories need to be offline.
  • Global: The whole organization is disconnected from remote repositories

Single Repository Offline

If a remote repository goes offline for any reason, Artifactory can be configured to ignore it by setting the Offline checkbox. In this case, only artifacts from this repository that are already present in the cache are used. No further attempt will be made to fetch remote artifacts.

Global Offline Mode

This is common in organizations that require a separate, secured network and are disconnected from the rest of the world (for example, military or financial institutions) .

In this case, remote repositories serve as caches only and do not proxy remote artifacts.

You can enable Global Offline Mode by setting the corresponding checkbox in the Admin tab under Configuration | General.

 

 

 

 

 

 

 

 

 

 

 

 

  • No labels