Re-evaluate need for the different "containered" builds that we do
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 重构
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, node.js
- 领域
- ci-cd, infrastructure
调研方向
Start by reviewing the listed containered build axes in the node-test-commit-linux-containered job, then compare how the Windows and ARM debug jobs run on PRs. Read the linked build issue about ARM container space for context. The issue is resolved when the discussion reaches a decision on which axes and debug builds to retain, move to daily runs, or change platforms.
由索引模型根据 Issue 内容生成。
描述
In node-test-commit-linux-containered we have the following build which are done on PRs (not necessatily all on each node version):
- ubi81_sharedlibs_openssl111fips_x64
- ubuntu2404_sharedlibs_debug_x64
- ubuntu2404_sharedlibs_icu_x64
- ubuntu2404_sharedlibs_openssl111_x64
- ubuntu2404_sharedlibs_openssl30_x64
- ubuntu2404_sharedlibs_openssl35_x64
- ubuntu2404_sharedlibs_openssl40_x64
- ubuntu2404_sharedlibs_shared_x64
- ubuntu2404_sharedlibs_smallicu_x64
- ubuntu2404_sharedlibs_withoutintl_x64
- ubuntu2404_sharedlibs_withoutssl_x64
- ubuntu2404_sharedlibs_zlib_x64
We should use this issue to discuss whether this is a suitable set of axis to build on.
A similar discussion should be had on the debug variants that we build for i.e. the node-compile-windows-debug and node-test-commit-arm-debug jobs. Do we still need those on every PR? It may be worth moving one or both of those to "daily" only. It's probably also worth trying to move the arm debug one back to x64 since that was mostly done for when we had the large equinix systems. The limited amount of space we have on the arm containered machines (I was looking at that recently in https://github.com/nodejs/build/issues/4534)
Two thoughts:
- Is Ubuntu 24.04 the most suitable platform to do all of these on?
- Could we have one "shared everything" axis which builds node as a shared library and also dynamically links to system shared libraries for SSL/ICU/zlib/anything else that we support on the system so we do them all together - and maybe have one older and one newer distribution to cover the ends of the spectrum (e.g. RHEL8 and Fedora latest? Those could be split over two architectures for additional coverage)
- 主要语言
- Jinja
- 星标
- 544
- 派生
- 184
- 平均合并
- 3 天 12 小时
- 30 天内合并 PR
- 7
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/build 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
nodejs/build#4539 · 1 个 reaction ·
维护者通常 2 天内回复
-
build-agenda
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 2 天内回复
-
难度 4/5 1-2 天 新手友好度 47/100
维护者通常 2 天内回复
-
Windows release nodes are offline可能已有人在做 @StefanStojanovic 于 1 天前认领。 未关闭
维护者通常 2 天内回复
相似的 Issue
-
simulator-session.yml の simtunnel の固定先が古く、agentd が無いため simtunnel up --wait / status が準備完了を検知できない未关闭
难度 2/5 1-3 小时 新手友好度 68/100
-
automated issue report
难度 2/5 1-3 小时 新手友好度 68/100
camunda/camunda-deployment-references#3903 ·
维护者通常 1 天内回复
-
VLAgent `spec.k8sCollector.includePodLabels: false` has no effect可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
VictoriaMetrics/operator#2772 ·
维护者通常 1 天内回复
-
admission-deferred priority: medium status: ready work-class: scoped
难度 2/5 1-3 小时 新手友好度 70/100
melodic-software/claude-code-plugins#10887 · 4 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
personalrobotics/geodude#243 ·
维护者通常 1 天内回复