-
Notifications
You must be signed in to change notification settings - Fork 948
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] How to distribute different content to different consumers #14281
Comments
Hi @maitrey First a quick question. |
The model is a simulink model and yes it lives in a git repository. |
Thanks for the info. Then the access to the model best approach could be via the This way, the access to the source code is done via the standard access to the git repo. Those with access to the git repo can build from source, and see the source, those without access to the git repo will only be able to use the pre-compiled binaries exclusively, and if they try to build from source, it will fail telling them they don't have permissions to the model source repo. Then, to provide different level of access to different customers to different packages, definitely the recommended way is setting up a different repository for each customer. |
We donot want to give customers access to our repository. We wanted to manage it via artifactory as a distribution platform. :( |
But this is what I am saying, setting up different Artifactory repositories, one for each customer, in Artifactory, with different permissions, and distribute via Artifactory. So you don't have to give access to your main Artifactory repositories to the customers, just to their own dedicated ones. I think there is something that I might not be understanding. |
Then we are on the same page but question is in order to repackage the content belonging to each customer artifactory repo , I need to take care of mapping PREV with RREV incase if there are multiple versions of the same package. Also for traceability reasons, I need to additional information to the re-packaged content , is my understanding right? |
But no need to re-package, you can just copy packages from your own repository to the customer repository. If you have already the package and it is working fine, why creating another? There are still things that I don't understand.
Sorry, I don't know what you mean. Yes, you need to copy to your customers repositories the packages you want, the versions you want with the revisions you want, like every release process, you don't release every commit, you pick one and make a release out of it, same but with package binaries, isn't it?
You mean adding properties in Artifactory? what "additional information"? |
James you meant copy packages and I meant makinga recipe and downloading it and repackage like : https://docs.conan.io/1/creating_packages/existing_binaries.html |
Do you mean that you use
Adding the
The git tag of the original source to build the package is intrinsic part of the recipe, typically the I am afraid that I don't understand neither the big picture nor the implementation, the naming/nomenclature used, the flows... |
'''
''' |
So are you hardcoding the full Artifactory URL down to the So it seems we are not talking really about different repositories in the server side, but about creating new packages from existing ones while breaking the dependency chain, for final distribution. It seems the ticket you want to track is this one: #13171 To extract binaries from Conan there are other recommended and documented mechanisms, like
Those, provided the right and common profiles, will do the task without needing to worry about the details of the URLs or hardcoding anything. The |
Okay james. Sorry, it took quiet some iteration to exactly explain what I had in mind(for that atleast you will remmeber me :D , I hope). Thanks for your inputs. I will try this and get back to you. |
To begin with , I tried to use full_deploy and direct_deploy. Both need a conanfile.txt. Is my assumption correct ? |
The CCI |
No, deployers can also work with any |
What is your question?
Dear Conan Folks,
We have a use case for example a component has a simulink model , we generate code at build time and compile it , generate the executable package it in 3 different variants(3 different compilers).
Now we have a requirement:
What would be the right way to proceed:
Is there a better way to handle such a use-case?
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: