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

オープン
#1,634 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR(30日)
376

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstackincubator/simlock のほかの issue

callstackincubator/simlock の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。