Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemotesManager should not change the order of the remotes #613

Open
Basti-D opened this issue Dec 6, 2022 · 0 comments · May be fixed by #614
Open

RemotesManager should not change the order of the remotes #613

Basti-D opened this issue Dec 6, 2022 · 0 comments · May be fixed by #614

Comments

@Basti-D
Copy link

Basti-D commented Dec 6, 2022

Problem

The RemotesManager changes the order of the remotes
When we define multiple remotes A, B, C, D, the RemotesManager adds B, C, D, A to Conan.
This changes the order of the remotes and influences artifact lookup.

The main problem arises when using the CONAN_UPLOAD repo and one download repo in CONAN_REMOTES.
Internally the upload repo will be appended to the CONAN_REMOTES.
Then we have the following order: CONAN_REMOTES=[download, upload] which is fine, since artifact retrieval will check the download repo at first.
But then the RemotesManager adds the repos in reveres order, i.e. conan gets the list [upload, download].
Hence conan will search for artifacts in the upload repo at first.
This yields to some problems in CI/CD.

@Basti-D Basti-D linked a pull request Dec 6, 2022 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant