mobile: preview Android builds lost the ADR-0047 speedups
维护者通常 1 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- android, github-actions
- 领域
- build-system, ci-cd, mobile
调研方向
Read ADR-0047 and ADR-0055, then inspect the preview, production and store profiles in mobile-app/eas.json and the ABI statement at mobile-app/docs/internal-builds.md:135. First determine whether preview APKs need x86 or x86_64 emulator support; the issue does not settle that decision. Then update the profile or ADR accordingly, align the documentation, and compare build times if changing the Gradle command.
由索引模型根据 Issue 内容生成。
描述
Context
ADR-0047 cut the Android job from about 22 minutes to 10–14 by building only armeabi-v7a and arm64-v8a, skipping lintVitalRelease, and passing --build-cache. These flags live in the gradleCommand of the production and store profiles in mobile-app/eas.json.
ADR-0055 later moved PR, dev, main and manual builds to the preview profile, which has no gradleCommand. Those builds therefore compile all four ABIs and run lint. ADR-0055 doesn't mention this, so it looks accidental.
Verified in main run 38869832335 (2026-10-16): Build Android (preview) ran plain gradlew :app:assembleRelease, with x86_64 and lintVital in its output. The job took about 15 minutes.
mobile-app/docs/internal-builds.md:135 also says the APK is built for two ABIs only, which isn't true of preview APKs.
Scope
- Decide whether preview APKs must install on x86/x86_64 emulators.
- If not, add the ADR-0047
gradleCommandto thepreviewprofile and compare build times. - If so, record that exception in ADR-0047.
- Either way, make
internal-builds.mdmatch.
Discussion / decisions needed
- Does anyone install preview APKs, and on what? They exist only as CI artifacts, kept for 14 days. If nobody installs them, the Android build on
mainis only a compile check.
Related
- 主要语言
- PHP
- 星标
- 26
- 派生
- 2
- 平均合并
- 2 天 19 小时
- 30 天内合并 PR
- 10
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Open-Locker/Open-Locker 的其他 Issue
-
mobile-app
难度 2/5 1-3 小时 新手友好度 74/100
Open-Locker/Open-Locker#352 ·
维护者通常 1 天内回复
-
docs
难度 2/5 1-3 小时 新手友好度 76/100
Open-Locker/Open-Locker#287 ·
维护者通常 1 天内回复
-
enhancement mobile-app
难度 4/5 一周以上 新手友好度 15/100
Open-Locker/Open-Locker#351 ·
维护者通常 1 天内回复
-
backend bug iot client
难度 4/5 3-5 天 新手友好度 25/100
Open-Locker/Open-Locker#350 ·
维护者通常 1 天内回复
-
backend iot client
难度 5/5 一周以上 新手友好度 35/100
Open-Locker/Open-Locker#345 ·
维护者通常 1 天内回复
查看 Open-Locker/Open-Locker 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
OpenConext/OpenConext-engineblock#2168 ·
维护者通常 5 天内回复
-
[Bug]: SCIM Users groups[].value is returned as an integer, causing authentik user discovery to fail未关闭
难度 2/5 1-3 小时 新手友好度 62/100
grokability/snipe-it#20006 ·
维护者通常 1 天内回复
-
fixed
难度 2/5 1-3 小时 新手友好度 62/100
firefly-iii/firefly-iii#13150 · 2 条评论 ·
维护者通常 1 天内回复
-
type/bug
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
TYPO3-Solr/ext-solr#4828 ·
维护者通常 5 天内回复