we are using GitLab in a multi project/package environment, given we started this long before the package registry existence, we are using a git based package manager quark.
Some projects are hard/long to build and so we created some
_output companion repositories to store the build artifacts to be retrieved via
This solution has an interesting side effect: we can use the same exact authentication mechanism (personal or deploy ssh keys) both locally and on the CI.
Let’s say we’d like to move towards using more the projects artifacts/registries, what is the suggested way to allow the same experience both locally and inside the CI?
We lived happily till now setting up an SSH key, so the option of manually create an access token, store it and manage it locally on multiple machines is a clear loss in UX (https://direnv.net/ exists and is a idea).
- can we automate the token creation to create a seamless experience? cli, remote ssh friendly automation
- may be possible to use ssh to (feature requests):
a) retrieve the artifacts from some sort of on-the-fly fake repo?
b) retrieve a temporary personal token that will work very like the
The b) option may allow a better experience using the
gitlab-runner exec feature.