I am using Gitlab to build a package that has a dependency on another package in a private registry.
After specifying CONAN_LOGIN_USERNAME: "ci_user" and CONAN_PASSWORD: ${CI_JOB_TOKEN} I can upload to the repo's registry. But even though I specify CONAN_LOGIN_USERNAME_other_repo: "ci_user" and CONAN_PASSWORD_other_repo: ${CI_JOB_TOKEN} conan cannot pull the dependency and always fails with conans.errors.NotFoundException: Unable to find 'my_package/1.0@company/stable' in remotes.
I checked the source code and to me it looks like remote authentication only happens for package uploads. Could that be?
It seems like CPT never tries to login to my other registry before trying to pull from there.
Description of Problem, Request, or Question
I am using Gitlab to build a package that has a dependency on another package in a private registry. After specifying
CONAN_LOGIN_USERNAME: "ci_user"
andCONAN_PASSWORD: ${CI_JOB_TOKEN}
I can upload to the repo's registry. But even though I specifyCONAN_LOGIN_USERNAME_other_repo: "ci_user"
andCONAN_PASSWORD_other_repo: ${CI_JOB_TOKEN}
conan cannot pull the dependency and always fails withconans.errors.NotFoundException: Unable to find 'my_package/1.0@company/stable' in remotes
. I checked the source code and to me it looks like remote authentication only happens for package uploads. Could that be? It seems like CPT never tries to login to my other registry before trying to pull from there.Environment Details