Using the latest version?
JFrog Platform User Guide
JFrog Artifactory 6.x Documentation
To get the latest version, go to the JFrog Unified Platform
Type-Specific Basic Settings
Repositories may have additional Basic settings depending on the Package Type.
Maven, Gradle, Ivy and SBT Repositories
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:
|
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.
Browsing Remote Repositories
In some cases, the remote resource that Artifactory proxy's supports remote browsing. In these cases, you can browse the contents of these repositories directly from the Artifactory UI.
For example, JCenter and Maven Central support remote repository browsing, however, Docker Hub does not. In the example below, Artifactory is showing the contents of JCenter.