The Advanced Settings can be found under the Admin tab and then Configuration -> Repositories and then click on New or select an existing remote repository to edit.
|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 occurs if the remote layout is different to 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).
|Suppress POM Consistency Checks||Whether the repository should suppress POM consistency checks.|
|Proxy||The network proxy reference.|
|Local Address||The local address to be used when creating connections. Useful for specifying the interface to use on multi-homed systems.|
|Username||The HTTP authentication username.|
|Password||HTTP authentication password.|
Network timeout in milliseconds to use both for connection establishment and for unanswered requests.
Timing out on a network operation is considered as a retrieval failure.
|Keep Unused Artifacts (Hours)|
The numbers of hours to wait before an artifact is deemed "unused" and eligible for cleanup from the repository.
A value of 0 means automatic cleanup of cached artifacts is disabled.
|Retrieval Cache Period (Secs)||The number of seconds to cache artifact lookup results. A value of 0 indicates no caching.|
|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 indicates the repository is never assumed offline.
|Missed Retrieval Cache Period (Secs)||The number of seconds to cache artifact retrieval misses (artifact not found). A value of 0 indicates no caching.|
Custom HTTP query parameters that are automatically included in all remote resource requests.
For example: param1=val1¶m2=val2¶m3=val3
|Eagerly Fetch Jars||When selected, the repository attempts to eagerly fetch the jar in the background each time a POM is requested.|
|Eagerly Fetch Sources||When selected, the repository attempts to eagerly fetch the source jar in the background each time a jar is requested.|
|Hard Fail||Whether failing to communicate with this repository returns an error to the client that causes the build to fail.|
|Do Not Store Artifacts Locally|
Whether the repository should store cached artifacts locally or not.
When not storing artifacts locally direct repository-to-client streaming is used.
This can be useful for multi-server setups over a high-speed LAN, with one Artifactory caching certain data on a central storage and streaming it directly to satellite pass-though Artifactory servers.
|List Remote Folder Items|
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||Whether to synchronize properties of artifacts retrieved from a remote instance of Artifactory.|
|Allow Archive Browsing|
Whether to allow unsafe archive content browsing - determines whether viewing archive content (e.g., Javadoc browsing) directly from Artifactory is permitted.
Allowing content browsing requires strict content moderation to make sure malicious users do not upload content that is used to compromise security.
For example: to conduct cross-site scripting attacks.
|Reject Invalid Jar Archives|
Reject the caching of jar files that are found to be invalid.
For example: pseudo jars retrieved behind a "captive portal".
You can instruct a remote repository to automatically eagerly retrieve related artifacts, in parallel on the server-side, before requested by the Maven client.
The options are:
- Try and fetch a
*.jar immediately when
*.pom is queried.
- Try and fetch a
*.jar is queried.
Having these options activated speeds up first downloads by a factor.
Suppressing POM Consistency Checks
By default, Artifactory keeps your repositories healthy by refusing bad POMs deployed on remote repositories with wrong information.
Artifactory checks that the coordinates (path) of POMs retrieved remotely match the
groupId:artifactId:version information inside the POM, and rejects POMs that conflict with their path.
You can disable this behavior by marking the 'Suppress POM Consistency Checks" checkbox.
Cleaning-up Unique Snapshots
If the remote repository managed unique snapshots names (the same
groupId:artifactId:version has many jars and pom with date and build number), you can configure Artifactory to automatically clean up old unique snapshots by setting the repository's
Max Unique Snapshots value to the maximum number of unique snapshots of an artifact that should be maintained in the repository. Clean up takes effect each time a new snapshot file name is downloaded and cached.
Remote Repository Authentication
If a remote repository requires authentication you can provide a
password as part of the repository definition.
Custom HTTP Query Parameters
Custom HTTP queries parameters that are automatically included in all remote resource requests. For example: param1=val1¶m2=val2¶m3=val3
List Remote Folder Items
If you want to browse the contents of a remote repository that has not been cached yet, you can enable this checkbox. This allows to navigate the contents of the remote repository via the Simple Browser or List Browser.
Proxying Maven 1 repositories
To proxy Maven 1 repositories, simply set the remote repository layout to Maven 1.
Connecting from Multi-homed Machines
If you are running Artifactory on a machine with multiple network interfaces and only specific interfaces can connect to remote repositories, you can specify the interface you want to use for remote connections under the "Local Address" field.