Use CI/CD to update to update the Conan Repository
Problem to solve
The GitLab Conan Repository allows C/C++ developers to create, share and discover their packages all from within GitLab. The MVC only supports authenticating with Personal Access Token.
In order to integrate with GitLab's CI/CD product and allow developers to build and publish their packages programmatically, we must allow users to authenticate with CI_JOB_TOKEN.
Intended users
Proposal
Support authentication of the Conan Repository with CI_JOB_TOKEN. Once a user has configured their repository to work use the GitLab Conan Repository, they will configure their CI/CD to build new packages automatically.
Further details
Permissions and Security
The permissions will not change. Users with access to a given instance, group or project will be able to pull or publish according to their role.
| Action | Guest | Reporter | Developer | Maintainer | Owner |
|---|---|---|---|---|---|
| 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 |
Documentation
- Update the docs to include details and examples of authenticating with CI_JOB_TOKEN.
Testing
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