When we create a remote repository, some remote repositories show the list of artifacts that are available in upstream registry and some do not show the list of artifacts even if artifacts are available in upstream.
The upstream registry artifacts will be visible in Artifactory remote repository when only upstream registry supports content browsing. If upstream registry does not support content browsing, Artifactory remote repository displays no artifacts, however we will be able to resolve the artifacts.
For example, a maven remote repository lists the contents in tree browser as below which is pointing to https://repo1.maven.org/maven2/
An Alpine remote repository lists the contents as below which is pointing to http://dl-cdn.alpinelinux.org/alpine
Below are the package types that support remote repository listing which are pointing the default upstream registries as of today.
Debian, Alpine, Conda, Gradle, Gems, Ivy, Opkg, Pub, Rpm, Sbt, Cargo.
Below are the package types that does not support remote repository listing which are pointing the default upstream registries.
cocoapods, Nuget, Docker, Nuget, Bower, Chef, Conan, Cran, Go, Npm, Php, Puppet, Pypi, terraform
Difference between Remote and Remote-cache repositories
Whenever we create a remote repository for the corresponding packages, it will automatically create a remote-cache repository along with the respective Remote Repository.
The files that we download from remote repository will only be visible in remote cache as they will be cached in Artifactory.
Why do we see the message “This item not cached”
When browsing the contents of a repository on selecting few artifacts, we might see a message “This item is not cached” as shown below.
This indicates that this artifact is not yet downloaded via Artifactory from upstream registry. Once we download the same artifact, this informative message will disappear.