To configure a remote repository, hover over it with your mouse and select "Edit" to display the Edit Remote Repository dialog.
Common Basic Settings
The following are fully described in the Common Settings page.
Additional Basic Settings
The URL for the remote repository. Currently only HTTP and HTTPS URLs are supported.
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:
- Generate if absent (default): Artifactory attempts to retrieve the 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.
- 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.
- 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.
- 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.
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.
If set, the configuration details of this repository are shared with remote clients (e.g. other Artifactory servers) and can be imported by them. For example, this can be useful if your organization maintains several instances of Artifactory, and you want to share remote repository configurations between them.
For details, please refer to Shared Repository Configurations.
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.