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

[question] Recommended way to mirror CCI recipes with source changes #17983

Open
1 task done
Totollie opened this issue Mar 18, 2025 · 1 comment
Open
1 task done

[question] Recommended way to mirror CCI recipes with source changes #17983

Totollie opened this issue Mar 18, 2025 · 1 comment
Assignees

Comments

@Totollie
Copy link

What is your question?

Hi team, I am looking into the best way to use CCI as a part of my group. We have a few challenges that make it potentially less straightforward. We will need to mirror all of the binaries from external vendor sites to our own storage for various checks, before they are consumed by Conan. By mirroring the binaries internally, we will be reducing risk from those binaries changing upstream and quietly invalidating those checks. Taking CMake as an example, the recipe's conandata.yml lists several download URLs for the binary contents. In this case we would want to copy those binaries into a similar path in our storage, run checks against those binaries separately, and have Conan fetch the binaries from that storage instead of the links checked into CCI. We would likely want to do similar with source repositories.

What would be the recommended approach to handle this? Should we fork CCI, patch the recipes, and rebase regularly (are there examples of this being done)? Or is there a mechanism within Conan 2 to replace a given set of URLs with another one? Thank you!

Have you read the CONTRIBUTING guide?

  • I've read the CONTRIBUTING guide
@memsharded memsharded self-assigned this Mar 18, 2025
@memsharded
Copy link
Member

Hi @Totollie

Thanks for your question.

Have you checked this section in the docs? https://docs.conan.io/2/devops/using_conancenter.html

There it recommends for some production cases not to mirror the binaries, but to actually build them in the org CI and upload your own binaries to your own private server.

The "local-recipes-index" feature in https://docs.conan.io/2/devops/devops_local_recipes_index.html is intended to use a fork of conan-center-index more easily to build the binaries.

Then, a different issue is the URLs of the external sources, there are 2 different strategies here:

Please let me know if this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants