Allow access to build artifacts by using restricted access tokens
Currently to access build artifacts for the following reasons:
- Access build artifacts of another (private) project during CI.
- In general allow an automated process to access the build artifacts.
there is only the way by using Personal Access Token. However for both situations it seems not to be a good idea to use a personal access token as it exposes too many features and could easily get abused by another person having access to the same project.
I think right now for private projects there is no way to access the build artifacts except the method using personal access tokens. This is a shortcoming and I think there should be a way for an automated process to have access to the build artifacts whithout using the personal access tokens.
I have found https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/157 which allows to pass artifacts within one projects but not across project boundaries.
I found gitlab-ce#19095 which is something that I am very interested in, but think that this is an overkill for project like gitlab. Having the artifacts and a way to access these in an automated manner also would allow to implement whatever package manager you like, on top of it.
I found gitlab-ce#4255 which is also cool, as it simplifies the access to specific artifacts. However from my point of view gitlab-ce#4255 is nearly useless if there is not a way to access the build in an automated manner.
I found gitlab-ce#4194 which asked how to access the source of another private project during CI. The Answer to this was, to use the deploy key. So there is a way to access the source of another project during ci, but there is no way to access the build artifacts of another projects during CI.
The request of the issue in short is: Allow to access the artifacts of a private project with a restricted access token which is not tied to a user but rather to a project.