If the proxy repository Negative Cache is enabled and the remote repository response indicates that the component was not found, then the proxy repository caches a record of that event. When a client requests a component that is not yet stored in the proxy repository, a request is made to the remote repository being proxied. A value of 0 will always check for new versions. A value of -1 will prevent the proxy from ever checking for new versions, which in most cases is not desirable. If the requested version is included in the updated metadata then the new version of the component can be retrieved from the remote to the proxy. When a client requests a version of a component not already cached and the metadata max age has expired, Nexus Repository Manager will ask the remote what versions are available for the component. The cache stores metadata about the versions of components available in the remote repository. If a client requests a component that already exists in proxy cache and the maximum component age has expired, the proxy will check whether this version of the component has been redeployed on the remote. For a docker proxy repository, a component would usually be a tagged image, so the default max component age is set to 1440 minutes. If the repository being proxied allows redeploy of existing components then you should configure the proxy to check for updates periodically. In most cases, components are considered immutable and will not change, in which case this value can be set to -1 to disable checking the remote repository for redeployed components. This setting controls whether a client request will cause the proxy to check for changes to previously cached components on the remote repository being proxied. Cache SettingsĬaching is configured in the settings of each proxy repository. The settings you can use to configure caching are described in this article. Proxy repositories use caching to improve build performance.
0 Comments
Leave a Reply. |