Provide build artifacts
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- perl
- 领域
- build-system, ci-cd, release
调研方向
首先阅读讨论 #1304 以及仓库的 Travis CI 和 Dist::Zilla 配置；issue 中将它们列为入口。比较 release-artifact 和 default-branch 的构建方案；完成的标准是确定一种经过同意和测试的方式，用于发布可用的预构建工件，而不要求完整的创作环境。
由索引模型根据 Issue 内容生成。
描述
User story
As a package maintainer,
I would like to use pre-built artifacts for packaging,
so I can avoid pulling in the whole authoring environment as build dependencies.
Describe the solution you'd like
The idea is to save the build results for each successfully tested commit of the default git branch, and ask Travis CI to publish them somewhere (e.g. in a separate branch, or repo). That way package maintainers may decide between using these pre-built "git builds" as installation source, packaging the whole build system, or anything in between (e.g. drop the author plugins, and only package the rest).
- idea 1: save build directory (or tarball) of tagged releases as standard GitHub Releases
- idea 2: save build directory (or tarball) of each successfully built commit from the default git branch ("bleeding edge builds")
Describe alternatives you've considered
See the discussion #1304. That is originally about implementing the patching logic which can be executed during package build time, but also touches using vendor-specific dist.ini files, or just maintaining the diff for them (ideally the discussion could have taken place in an issue first, but I don't want to duplicate everything by copying text over here now).
I'm also not comfortable bringing in vendor-specific packaging details into the project scope, mostly because if a vendor would like to build Rex differently than upstream, that is great, but I think it still primarily is a decision and concern of the vendor. That may be rephrased as: "we supply how we intend Rex to be built; that's completely fine if you have a different opinion, and feel free to build it differently, but that's your choice".
Additional context
The build process of Rex relies on various Dist::Zilla plugins. Some of it is important only for authors (people who modify Rex itself), and strictly speaking only the rest are important for end-users (people who want to build and install Rex). Furthermore, there's a distinction between tagged releases and building from the default git branch.
OS packages for tagged releases can use pre-built sources e.g. from CPAN (while it would also be nice to upload these tarballs as GitHub Releases as well). But if you'd like write a package that builds Rex from source (like a specific commit or branch), the whole list of build dependencies has to be pulled in. That might impose a prohibitive cost on the packaging side, with relatively low returns in exchange (e.g. using Test::PerlTidy to ensure that the source code is tidy: it's mostly important for authors to keep the code style consistent, but less important for end-users who only want to run Rex).
- 主要语言
- Perl
- 星标
- 736
- 派生
- 217
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
RexOps/Rex 的其他 Issue
-
is_redhat() misses Rocky/Alma/CentOS Stream/Oracle Linux lsb_release IDs -> pkg dies "OS/Provider not supported"可能已有人在做 @stantheman0128 于 24 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
-
bug
难度 3/5 1-2 天 新手友好度 45/100
-
triage needed
难度 4/5 3-5 天 新手友好度 35/100
-
bug
难度 3/5 1-2 天 新手友好度 35/100
-
triage needed
难度 3/5 1-2 天 新手友好度 42/100
相似的 Issue
-
observablt-ci
难度 2/5 1-3 小时 新手友好度 86/100
elastic/golang-crossbuild#840 ·
维护者通常 1 天内回复
-
Sync playback crashes repeatedly in a sync group (v9.1.1)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
LMS-Community/slimserver#1701 · 6 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
RotherOSS/otobo#6286 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
-
fix(api): API v3 Product Read ignores request language (lc) for sample products and image URLs可能已有人在做 @muntasir-396 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
openfoodfacts/openfoodfacts-server#15042 · 1 条评论 ·
维护者通常 1 天内回复