This section examines the settings used by remote repositories for deciding how to handle remote artifact requests.
When a remote artifact is stored in Artifactory, it is cached for a certain and controlled period of time. For Maven artifacts, this is applicable only for snapshots, since releases are assumed never to change.
When Artifactory receives a request, where an artifact that its caching timeout has expired, Artifactory checks if there is an updated artifact remotely.
|Repository Layout||Select the layout the repository to be used for storing and identifying modules.|
|Remote Layout Mapping|
Select the layout that best matches the layout used by remote repository for storing and identifying modules.
Path-mapping takes place if the remote layout is different from the local layout - remote module artifacts and descriptors are stored according to the local repository layout (e.g., Maven 1->Maven 2, or Maven 2->Ivy).
|Proxy||Network proxy reference|
The local address to be used when creating connections.
Useful for specifying the interface to use on multi-homed systems.
|Username||Enter the HTTP authentication username.|
|Password||Enter the HTTP authentication password.|
This is the timeout period (for socket and connection) that Artifactory waits for before giving up on retrieving an artifact from a remote repository. After a timeout Artifactory caches the fact that a retrieval failure has happened for the amount of time defined in "Failed Retrieval Cache Period".
Artifactory answers future requests for that particular artifact with
NOT_FOUND (404) for a period of "Failed Retrieval Cache Period" seconds and does not attempt to retrieve it it again until that period expired.
|Keep Unused Artifacts (Hours)||Many cached artifacts in Artifactory remote repository storage are actually unused by any current projects in the organization. To solve this issue you can set an automatic removal of unused artifacts in remote repository caches.|
|Retrieval Cache Period (Secs)||Defines how long before Artifactory checks for a newer version of a requested artifact in remote repository. Artifactory will not fetch anything but the metadata if no newer version is found.|
|Assumed Offline Limit (Secs)||The number of seconds the repository stays in assumed offline state after a connection error. At the end of this time an online check is attempted in order to reset the offline status.|
A value of 0 means the repository is never assumed offline.
|Missed Retrieval Cache Period (Secs)||The number of seconds to cache artifact retrieval misses. A value of 0 means no caching.|
A miss is a 404 response (
NOT_FOUND) received from a remote repository that currently does not have the artifact requested. You might want to treat this differently than when failing to retrieve the artifact is due to network problems.
You can clean up the Retrieval Cache by selecting a cached file or a folder in the Artifacts tab and then
Tree Browser and clicking (or selecting, if right-clicking the item) the "Zap Caches" action.
You can cleanup both the Retrieval Failures Cache and Missed Retrieval Cache by selecting a cached folder in
Artifacts -> Tree Browser and clicking (or selecting, if right-clicking the item) the "Zap Caches" action.