-
Notifications
You must be signed in to change notification settings - Fork 82
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
Use GitLab generic packages repository for assets #174
Comments
@walkafwalka Thanks for this! I agree that the Generic Package Registry is a better fit. In fact, this is the direction GitLab itself is taking (see https://gitlab.com/gitlab-org/gitlab/-/issues/255271#note_453907441 and https://gitlab.com/gitlab-org/release-cli/-/issues/68). I would suggest we wait until GitLab has landed on an specific approach and then updating this plugin to mirror its behavior. |
I think this has happened now: https://docs.gitlab.com/ee/user/project/releases/#use-a-generic-package-for-attaching-binaries |
I have also an error uploading file with size greater than 100Mb:
Can I try to post a PR? |
…#343) Co-authored-by: Florian Greinacher <[email protected]>
This is now possible, thanks to @JonasSchubert work in #343 🎉 |
The GitLab generic packages repository is more suited for storing assets related to releases.
And unlike the current project uploads API, the documentation explicitly states that the CI_JOB_TOKEN has access to the Packages API.
The text was updated successfully, but these errors were encountered: