Open samuel-emrys opened 2 years ago
This doesn't seem a Conan issue, but an Artifactory one.
It seems that the default behavior of Artifactory virtual repository is to cache the remote that was used in the resolution of the recipe and forward search requests to that other repo. But I am no expert in Artifactory.
So I would recommend the following:
@memsharded no worries, thanks for the direction. I wasn't sure where the lines blurred between the conan team and the artifactory team when it came to conan. I'll post a ticket there when I get a chance.
https://www.jfrog.com/jira/browse/RTFACT-26879 for tracking
This is an issue where when a virtual repository contains both a remote repository and a local repository, only the remote repository will be searched when invoking
conan search
, despite the local repository containing non-default configured binaries that will install successfully.Environment Details (include every applicable attribute)
Steps to reproduce (Include if Applicable)
conan-center-builds
is the local repository deployment target ofconan-center-virtual
andconan-center-remote
is the remote repository pointing at https://center.conan.ioNote that this will return no results, because
conan-center-builds
is not searched. It will however return results forconan-center-remote
. I get 72 configurations without grepping the above command.Logs (Executed commands with output) (Include/Attach if Applicable)
To demonstrate that this does actually return results: