git - 如何在 GitLab 中存储发布/二进制文件？

Question

我正在使用 Gitlab、Jenkins 和 - 可能 - Nexus(我需要一个工件存储)构建一个工作流程。我想让 GitLab 存储发布/二进制文件 - 是否有可能以方便的方式？

我不希望有其他服务可以从中下载版本(和文档)，而是希望以某种方式将它与存储库管理器集成，就像在例如中处理版本一样GitHub。有什么线索吗？

Answer 1

2020 年 10 月更新:

GitLab 13.5现在提供:

Attach binary assets to Releases

If you aren’t currently using GitLab for your releases because you can’t attach binaries to releases, your workflow just got a lot simpler.

You now have the ability to attach binaries to a release tag from the gitlab.ci-yml. This extends support of Release Assets to include binaries, rather than just asset links or source code. This makes it even easier for your development teams to adopt GitLab and use it to automate your release process.

See Documentation and Issue.

---

2015 年 11 月更新:GitLab 8.2 now supports releases .

有了它的 API，您现在可以 create and update a relase associated to a tag .
目前，只有将发行说明( Markdown 文本和附件)添加到 git 标签(又名发行版)的功能。

• 第一个upload发布二进制文件
• create a new release并在描述中放置指向上传的二进制文件的链接

2019 年 5 月更新:GitLab 1.11 引入了一个有趣的“Guest access to Releases”:

It is now possible for guest users of your projects to view releases that you have published on the Releases page.
They will be able to download your published artifacts, but are not allowed to download the source code nor see repository information such as tags and commits.

---

2015 年 3 月的原始答案

这正在进行中，并在 suggestions 4156755 中提出建议:

We’re accepting merge requests for the minimal proposal by Ciro:

1. For each repository tag under https://github.com/cirosantilli/test/releases/tag/3.0, allow to upload and download a list of files.2. The upload and download can be done directly from the tag list view.3. If a tag gets removed, the uploads are destroyed.(we’re not accepting the tag message edit mentioned in recent comments)

---

对该建议的评论包括:

What makes it more interesting is the next step.
I would really like a way to let public download artifacts from "releases" without being able to access source code (i.e. make sources private for project team only except anything else like wiki, "releases", issue tracker).

However, such additional feature looks more generic and I submitted a separate feature request for that.

Nevertheless, I repeat my point here:
While the simplistic version of "releases" is still nice to have, many people can easily set up external file server and point URLs in release/tag description to this server outside GitLab.
In other words, "releases" may not look attractive now without some future picture of integration.