If set to true, Artifactory will never try to fetch artifacts remotely. Only cached and local artifacts will be served. The maximum size in megabytes for uploaded artifact files. Set to '0' for unlimited size. The format used for displaying dates. Addons related configuration. Mail server related configuration. Security related configuration used in authentication and authorization. A set of backup configurations. A set of locally installed repositories. A set of remote proxied (normally cached) repositories. A set of virtual repositories wrapping regular local and remote repositories. A set of reusable proxy definitions. Proxies can be used by remote repositories by assocating a proxy definition with a remote repository. Define property sets to group together properties of the same category (e.g. QA). Then, define properties and their respective possible values (e.g. performance:{poor,acceptable,good} and qaStaffComment:[any]). Once property sets and their properties are defined, you may associate them with repositories, in order to be able to easily set, update and search for predefined property values on hosted repository items. A hard-coded URL prefix used by Artifactory for calculating relative URLs. Use this only if you need to override the default URL base (equals to the Servlet context URL - e.g. http://myhost.com/artifactory). A remote URL of a logo image. Additional custom text to appear on the page footer. Whether to use time-based version numbers for the name of SNAPSHOTs, or to use a non-unique, self-overriding naming pattern of artifactId-version-SNAPSHOT.type (the default), or to respect the deployer settings coming from the Maven client. Checksum policy determines how Artifactory behaves when a client checksum for a deployed resource is missing or conflicts with the locally calculated checksum (bad checksum). Checksum checking effectively verifies the integrity of the deployed resource. The options are: (1) Verify against client checksums (default) - Until a client has sent a valid checksum for a deployed artifact that matches the server's locally calculated checksum, the artifact will not be available and will return 404 (not found). If the client has sent a checksum that conflicts with the one calculated on the server a 409 (conflict) will be returned until a valid checksum is deployed. (2) Trust server generated checksums - Do not verify against checksums sent by clients and trust the ones store server's locally calculated checksums. An uploaded artifact will be available for consumption immediately, but integrity might be compromised. Whether the repository is blacked-out. A blacked-out repository does not participate in artifact resolution, nor does its local cache. Whether the repository handles release artifacts. Whether the repository handles snapshot artifacts. The maximum number unique snapshots (of the same artifact) to store. Any number of snapshots above the max will be automatically removed by age. A value of 0 (the default) means no limits on unique snapshots number (thus no automatic cleanup). Whether the repository should suppress pom consistency checks. The property sets that users will be able to use of items hosted under this repository. As property sets are purely assistive and not enforcing, setting this on a repository only affects the list of predefined properties in the user interface properties tab for items under the repository. You will still be able to attach arbitrary properties to repository items. A property set usable by this repository. Repository unique id. Textual description of the repository. Optional notes about this repository. The type of the repository, which normally also reflects on its layout and behavior. Comma-separated list of artifact patterns to include when evaluating artifact requests, in the form of x/y/**/z/*. When used, only requests matching one the include patterns will be served. By default all artifacts are included (**/*). Comma-separated list of artifact patterns to exclude when evaluating artifact requests, in the form of x/y/**/z/*. By default no artifacts are excluded. HTTP authentication username. 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. The local address to be used when creating connections. Useful for specifying the interface to use on multi-homed systems. Network proxy reference. The url for the remote repository. Currently only HTTP urls are supported. When set to true only already-cached artifacts will be retrieved and fetching remote artifacts will not be attempted. Whether failing to communicate with this repository will return an error to the client that will fail the build. 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. When selected, the repository will attempt to eagerly fetch the jar in the background each time a pom is requested. When selected, the repository will attempt to eagerly fetch the source jar in the background each time a jar is requested. The number of seconds to cache artifact lookup results. A value of 0 means no caching. The number of seconds to cache artifact retrieval failures (resulting in comm. errors). A value of 0 means no caching. The number of seconds to cache artifact retrieval misses (artifact not found). A value of 0 means no caching. Checksum policy determines how Artifactory behaves when a checksum for a remote resource is missing or conflicts with the locally calculated checksum (bad checksum). Checksum checking effectively verifies the integrity of the remote resource. The options are: (1) Generate if absent (the default) - A bad remote checksum will fail the resource request. If, however, a remote checksum could not be found Artifactory will automatically generate one. (2) Fail: A bad or missing remote checksum will fail the resource request. (3) Ignore and generate: Artifactory will locally generate a checksum for both bad or missing remote checksum. Remote resource retrieval will never fail, but integrity might be compromised. (4) Pass-thru: Artifactory will store and pass-thorugh all remote checksums including bad ones and will locally generate a checksum for a missing remote checksum cannot be found. Remote resource retrieval will never fail, but integrity might be compromised and client-side checksum validation (such as the one done by Maven) will fail. Whether or not to enable automatic cleanup of cached artifacts that were not used for over a predefined period of time. The numbers of hours to wait before an artifact is deemed "unused" and eligible for cleanup from the repository. Whether or not the configuration details of this remote repository can be publicly shared with remote clients, such as other Artifactory servers. Whether to synchronize properties of artifacts retrieved from a remote instance of Artifactory. Determines whether artifact requests coming from other Artifactories can be fulfilled by accessing this virtual repository's remote repositories or by only accessing its caches (the default). A set of local and remote repository references to include in a virtual repository. A named key-pair to use for automatically signing artifacts. (1) Discard Active References - Will removes repository elements that are declared directly under project or under a profile in the same pom that is activeByDefault. (2)Discard Any References - Will removes all repository elements regardless of whether they are included in an active profile or not. (3)Nothing - Don't removes any repository elements declared in the POM. Local, remote or virtual repository reference (key). Proxy unique id. Proxy host. Proxy port number. Proxy username. Proxy password. The computer name of this machine (the one connecting to the NTLM proxy). Proxy domain/realm name. Make this proxy the default for new remote repositories and for internal HTTP requests. Backup unique id. Determines whether this backup is enabled or disabled. More Info... ]]> The maximum number of hours to keep old backups in the destination dir. Checking the "Incremental" checkbox, means that backups will be incrementally (delta only) written to the same directory: ${backupDir}/current. This "in place" backup type is suitable for file-system based backup support, and cleanup of old backups is inactive in this mode. The default is 168 hours = 7 days. Determines whether the backup output should be a zip archive or a directory (the default). A set of repository references to exclude from backup. Local or remote repository reference (key). Send email notifications to admin users if errors were encountered during the backup process (requires properly configured email settings and valid email addresses for admin users). Configuration for the indexer creating (Nexus) indexes downloadable by IDEs. Determines whether the indexer service is enabled and should be run. A set of repository references to exclude from indexing. Repository reference (key). When selected, info about available add-ons will show up in the Artifactory user interface. Enabling add-ons info display will reset any user-specific info-hiding preference. A variable used for calculating the path for a user cookie storing his personal add-on info showing preferences. The host name of the mail server. The mail server's port. The authentication username. The authentication password. The "from" address header to use in all outgoing mails. Can be left blank. A prefix to use for the subject of all outgoing mails. Determines whether to use transport layer security when connecting to the mail server. Determines whether to use SSL when connecting to the mail server. Determines whether anonymous access to the repository and the UI is permitted. When checked, Artifactory will hide the existence of unauthorized resources by sending a 404 response (not found) to requests for resources that are not accessible by the user. Otherwise, the response will imply that the resource exists but is protected - by requesting authentication for anonymous requests (401) or by denying an authenticated request for unauthorized users. Determines the password requirements from users identified to Artifactory from a remote client, such as Maven. The options are: (1) Supported (the default) - Users can authenticate using both secure encrypted passwords or clear-text passwords. (2) Required: Users need to authenticate using secure encrypted passwords. Clear-text authentication will fail. (3) Unsupported: Only clear-text passwords can be used for authentication. Ldap setting unique id. Determines whether this ldap is enabled or disabled. Determines whether users should be auto-created when using LDAP, otherwise they are transient and associated with auto-join groups defined in Artifactory. Ldap group setting search base. Ldap group setting search base. The Group name attribute. The group member attribute Flag whether to check the full subtree when searching The filter to search in the group The group description The group description A reference to the LDAP setting to retrieve this group. A unique name identifying the property set. Whether this property set will be visible in the properties management user interface, or is intended for internal use. The list of properties grouped under this property set. A unique name identifying the property. Whether the values of the property should come from a predefined closed list of values. Whether the property supports multiple values. A list of predefined values to select from for the property value(s). The actual value. Whether or not this value is a default/pre-selected one (multiple choice properties support multiple default values).