Open barnou-psee opened 4 hours ago
Hi @barnou-psee
Thanks for your question.
This is indeed a known issue, we have this ticket to track it: https://github.com/conan-io/conan/issues/16703 As you can see there, it is labeled as "complex:huge", because it is mostly a server-side issue, and that can be challenging and require time.
I saw there is a --only-recipe option that can be used to upload only the recipe, is there an opposite? liks --only-package maybe? Is it the objective of the -p option?
I think you are close to what would solve it. As Conan has checks to avoid uploading things that are already in the server, it is possible to do the following:
--only-recipe
in a single job, all the relevant recipes. The recipes are the ones that might case race conditions if uploaded concurrently at the very same timeThere could be other possible related approaches:
conan cache save/restore
together with Conan package-lists, to gather everything in CI side, then do a single upload with the recipe plus all the binaries, in a single job
What is your question?
Hello, in our CI we're building for different profiles and we're uploading them. Each profile is built in parallel and when published it happens that the upload steps doesn't see the recipe uploaded but when uploading it, another profile have done it already. How do you handle those cases? I saw there is a
--only-recipe
option that can be used to upload only the recipe, is there an opposite? liks--only-package
maybe? Is it the objective of the-p
option?Have you read the CONTRIBUTING guide?