The advanced settings for a remote repository configure repository layouts, network access behavior, cache management and several other parameters related to remote repository access.
To access the advanced settings, in the Edit Remote Repository dialog select the Advanced tab.
The Layout settings determine which layout Artifactory should use to cache artifacts downloaded from a remote repository, and how to map the local layout to the true layout used by the remote repository.
|The layout that should be used for storing and identifying artifacts in the local cache of the remote repository.|
Remote Layout Mapping
The layout that best matches the true layout used by remote repository for storing and identifying artifacts.
Artifactory will store remote artifacts and descriptors according to the Repository Layout specified and perform a path mapping if the Remote Layout Mapping selected is different (e.g. Maven 1-default to Maven 2-default).
Suppress POM Consistency Checks
By default, Artifactory keeps your repositories healthy by refusing POMs with incorrect coordinates (path).
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 Checks checkbox.
|If your organization requires you to go through a proxy to access a remote repository, this parameter lets you select the corresponding Proxy Key.|
For more details on setting up proxies in Artifactory please refer to Managing Proxies.
When working on multi-homed systems, this parameter lets you specify which specific interface (IP address) should be used to access the remote repository.
This can be used to ensure that access to the remote repository is not blocked by firewalls or other organizational security systems.
|The username that should be used for HTTP authentication when accessing this remote proxy.|
|The password that should be used for HTTP authentication when accessing this remote proxy.|
The time that Artifactory waits (for both a socket and a connection) before giving up on an attempt to retrieve an artifact from a remote repository.
Upon reaching the specified Socket Timeout Artifactory registers the repository as "assumed offline" for the period of time specified in Assumed Offline Limit.
Lenient Host Authentication
|When set, allows using the repository credentials on any host to which the original request is redirected.|
Enable Cookie Management
|When set, the repository will allow cookie management to work with servers that require them.|
Artifactory stores artifacts retrieved from a remote repository in a local cache. The Cache Settings specify how to manage cached artifacts.
Keep Unused Artifacts
Many cached artifacts in Artifactory remote repository storage are actually unused by any current projects in the organization. This parameter specifies how long an unused artifact will be stored before it is removed. A value of 0 means that the artifact is stored indefinitely.
Retrieval Cache Period
Defines how long before Artifactory checks for a newer version of a requested artifact in a remote repository.
A value of 0 means that Artifactory will always check for a newer version.
This setting refers to artifacts that may change (e.g. snapshots, metadata files etc.). Note that most artifacts that are downloaded do not change (e.g. release versions), therefore this setting has no effect on them.
Assumed Offline Limit
In case of a connection error, this parameter specifies how long Artifactory should wait before attempting an online check in order to reset the offline status.
A value of 0 means that the repository is never assumed offline and Artifactory will always attempt to make the connection when demanded.
Missed Retrieval Cache Period
If a remote repository is missing a requested artifact, Artifactory will return a "404 Not found" error. This response is cached for the period of time specified by this parameter. During that time, Artifactory will not issue new requests for the same artifact.
A value of 0 means that the response is not cached and Artifactory will always issue a new request when demanded.
"Zapping" a cache means forcing the Retrieval Cache Period and Missed Retrieval Cache Period to time out. To "zap" a cache, in the Artifacts tab select Tree Browser.
Select the repository cache you wish to "zap" and click the "Zap caches" button.
A custom set of parameters that should automatically be included in all HTTP requests to this remote repository.
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.|
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.|
|When set, Artirfactory will return an error to the client that causes the build to fail if there is a failure to communicate with this repository.|
Do Not Store Artifacts Locally
When set, Artifactory will not artifacts from this repository will not be cached locally. In this case direct repository-to-client streaming is used.
List Remote Folder Items
When set, lists the items of remote folders in simple and list browsing. Required for dynamic resolution depending on remote folder content information, such as remote Ivy version lookups.
The remote content is cached according to the value of Retrieval Cache Period
Synchronize Artifactory Properties
|When set, synchronizes properties of artifacts retrieved from a remote instance of Artifactory.|
Allow Content Browsing
When set, allows Artifactory users to browse the internal contents of archives (for example, browsing specific Javadoc files from within a Javadoc archive.
Reject Invalid Jar Archives
When set, rejects the caching of jar files that are found to be invalid.
For example: pseudo jars retrieved behind a "captive portal".