CI runs: prepare each leased device (language, reduce motion, permissions, keychain reset)

未关闭
#1,634 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript

调研方向

Start by reading the linked request #1294 and the spec discussion on #327, then compare the existing lease request and named baseline behavior. The issue leaves the central design choices open: whether to add settings to lease requests and whether keychain reset belongs here. Done means the team resolves those choices and defines how CI leases get devices into the required state.

由索引模型根据 Issue 内容生成。

描述

feature:spec

Request: #1294

Problem

A CI run that leases many devices has to prepare each one by hand. budgie's e2e suite (budgie-at/budgie#1867) runs simctl through POST /v1/leases/<id>/exec on every lease: keyboard and language (AppleKeyboards, AppleLanguages -array en-US), reduce motion, privacy grant contacts|microphone <bundle id>, and a keychain reset before each test, so a PIN one test set can't lock out the next. The lease request has no field for any of this; the Maestro setup it replaces had simulator-reduce-motion and simulator-device inputs.

A named baseline prepared with these settings covers most of it today, but that means one baseline per settings combination, set up by an operator, and the per-test keychain reset is not covered.

Split from #1633 (release every lease of a run) in the spec session of 2026-11-17: the two halves of #1294 share no decision.

Who it is for

A CI job that leases 5–10 simulators per run on a shared farm and needs each one in a known state before its tests.

Open questions

  • Is a named baseline the answer (then document how to make one for a CI suite), or should the lease request also take common settings (language/locale, reduce motion, permission grants for a bundle id)? A spec session on #327 (2026-11-02) kept the rule that Simlock copies devices and runs no setup of its own; settings in the request would change it.
  • Does a keychain reset belong here, or does it need its own call?

Written by an agent.

主要语言
TypeScript
星标
705
派生
40
平均合并
12 小时 9 分钟
30 天内合并 PR
376

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。