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

Ouverte
#1,634 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
typescript

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
705
Forks
40
Merge moyen
12 h 9 min
PR mergées (30 j)
376

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstackincubator/simlock

Toutes les issues de callstackincubator/simlock

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.