A remote repository serves as a caching proxy for a repository managed at a remote URL (which may itself be another Artifactory remote repository). Artifacts are stored and updated in remote repositories according to various configuration parameters that control the caching and proxying behavior.
You can remove artifacts from a remote repository cache but you cannot deploy a new artifact into a remote repository.
Artifacts in a remote repository can be accessed directly using the following URL:
http://<host>:<port>/artifactory/<remote-repository-name>/<artifact-path>
This URL will fetch a remote artifact to the cache if it has not yet been stored.
In some cases, it is useful to directly access artifacts that are already stored in the cache (for example to avoid remote update checks). Use the following URL to directly access artifacts that are already stored in the cache:
http://<host>:<port>/artifactory/<remote-repository-name>-cache/<artifact-path>
Proxy vs. Mirror
A remote repository acts as a proxy not as a mirror. Artifacts are not pre-fetched to a remote repository cache. They are only fetched and stored on demand when requested by a client.
Therefore, a remote repository should not contain any artifacts in its cache immediately after creation. Artifacts will only be fetched to the cache once clients start working with the remote repository and issuing requests.
 |