Project and Group level support for Conan Repository
Problem to solve
Conan is an open source C/C++ package manager that was designed to help developers create and share their binaries. Based on customer demand, the GitLab MVC prioritized supporting Conan at the instance level. However, in order to help organizations who have some groups working in C/C++ and others working in different languages, we need to support project/group level. This will allow engineers to focus by creating a more targeted, specific user experience. It will also allow organizations to structure their GitLab integration, similar to how they've structured their organization.
Add a project and group level endpoint to allow users leverage the Conan Repository at the Group level. This will also align our Conan Repository with how we've implemented Maven and NPM, creating feature parity and consistency.
Permissions and Security
There are no updates to permissions. Users that have access to a given project or group will have the the below permissions, which are consistent with GitLab's other package manager integrations.
|Pull from Maven repository or NPM registry or Conan Repository||x||x||x||x|
|Publish to Maven repository or NPM registry or Conan Repository||x||x||x|
- Update the docs at https://docs.gitlab.com/ee/user/project/packages/conan_repository.html to include project and group level details
- Test permissions work as expected at instance/group/project level
- Ensure there are no issues for instances that have the repository turned on at each level.
What does success look like, and how can we measure that?
What is the type of buyer?
This feature will be focused on Director and Executives, as it is a Premium/Ultimate feature. https://about.gitlab.com/handbook/ceo/pricing/#four-tiers