t1k:unity:mobile:floor-probing-jenkins
| Field | Value |
|---|---|
| Module | mobile |
| Version | 3.65.6 |
| Effort | medium |
| Tools | — |
Keywords: branches to build, CLOUDX, floor probing define symbol, floor probing jenkins, floor-probing jenkins, PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS, release branch jenkins, symbol-only, X_FLOOR_PROBING
How to invoke
Section titled “How to invoke”/t1k:unity:mobile:floor-probing-jenkins[--platform android|ios|both] [--symbol-only]T1K — Floor Probing Jenkins Define Symbol
Section titled “T1K — Floor Probing Jenkins Define Symbol”Without X_FLOOR_PROBING compiled in, the floor-probing config
(t1k-unity-mobile-floor-probing-config) is dead code — every gated call site (AppLovinAdsWrapper.cs,
CachedGridFloorLookup.cs) compiles out. This skill closes that gap on CI: idempotently append the
define symbol to the project’s Jenkins jobs.
- In scope, every mode: idempotently adding
X_FLOOR_PROBINGtoPARAM_UNITY_SCRIPTING_DEFINE_SYMBOLSon BOTH Develop and Release jobs, for whichever platforms are detected. Also: verifying/correcting the job’s git repo URL, and (Android, migrated-GDK case) offering to drop a staleCLOUDXsymbol. - In scope, full-pipeline mode only (no
--symbol-only): setting Branches-to-build on the project’s Release job(s) to the router-resolved release branch. --symbol-onlymode: symbol append only — no release branch is required as input, and Branches-to-build is never touched. Used by the router’s mode 2 (--with-jenkins), which wires the symbol without a PR, release branch, or push, AND by mode 3’s own step 3, which wires the symbol before the PR/merge and release push so no push in the pipeline — develop merge included — can ever land symbol-less.- Out of scope: creating new Jenkins jobs (
t1k-jenkins-unity), any other parameter, changing an iOS job’s branch (iOS jobs get the symbol only, in any mode — see Workflow), triggering a build directly via the Jenkins API (in full-pipeline mode the router’s own push step starts it via the GitHub push webhook).
Prerequisites — read before mutating anything
Section titled “Prerequisites — read before mutating anything”This skill reuses existing machinery rather than re-implementing config.xml mutation:
t1k-jenkins-jobSKILL.md — credential resolution order (env → registered Jenkins MCP → ask),list/get-config/update/verifycommands, the missing-<defaultValue>-element gotcha, and “never verify with the same helper you wrote with.”t1k-jenkins-unity/references/project-detection.mdandt1k-jenkins-unity/references/param-matrix.md— howPARAM_UNITY_SCRIPTING_DEFINE_SYMBOLSis read per platform (Android:/iPhone:keys) and the Develop/Release/Creative job-class conventions.
Workflow
Section titled “Workflow”- Detect platforms — does the repo have a
UnityAndroid/and/orUnityIOS/Jenkins folder (pert1k-jenkins-unity’s folder convention)? Use whichever exist; ask if ambiguous or neither is found. - Resolve job names by LISTING, never by assuming a name pattern:
node ~/.claude/skills/t1k-jenkins-job/scripts/jenkins-job.cjs list <folder> --grep <ProjectName>, then for each Develop/Release candidate,get-configit and read back the git repo URL — job names don’t always match the project (LifeChoicesrepo → jobLifeChoice-Release;TrickyChibi3-Releaseactually builds repoTrickyMonster).- Repo URL mismatch (observed:
RoleSwapSprunky-Releasestill built repoRoleSwapEmotionon branchsprunky/release-1.0.8) →AskUserQuestionwhether to switch it now (update <folder> <job> --repo <url>) before continuing, or skip this job.
- Repo URL mismatch (observed:
- Pre-flight on the Release job(s) — run the check itself regardless of
--symbol-only. Does it have a GitHub push trigger (verify <folder> <job> --expect-triggers yes, or readconfig.xmlforcom.cloudbees.jenkins.GitHubPushTrigger)? A--symbol-onlycall no longer means “no push is ever planned” — the router’s mode 3 uses--symbol-onlyfor its step 3, BEFORE the PR/merge and release push that follow in later steps, so a push is still coming even though this particular call doesn’t make it. Only ask when a push is imminent from THIS invocation (full-pipeline mode, not--symbol-only): if no trigger, this skill’s update alone will not start a build once the router pushes in its step 7 —AskUserQuestionwhether to trigger the Release build manually after this update lands, or proceed and leave it un-built for now. Under--symbol-only(mode 2, or mode 3’s step 3), report the trigger state in the step’s summary but do not ask — no push is planned by this call either way, and the later full-pipeline call re-checks it before its own push. - For each
(folder, job)pair,get-configand read the CURRENTPARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS<defaultValue>AND, for Release jobs, the current<hudson.plugins.git.BranchSpec><name>: a. Define symbol — split on;, check for an exact token match ofX_FLOOR_PROBING— never a substring check (X_FLOOR_PROBING_V2, or any symbol merely containing the string, must not count as already-present). Absent → append;X_FLOOR_PROBING, preserving the existing separator/whitespace convention; never remove or reorder any other token. b. StaleCLOUDX(Android jobs on a migrated GDK that now prefers AppLovin) — if the define-symbol string still carries aCLOUDXtoken,AskUserQuestionwhether to remove it; never remove it silently. c. Branch — Release jobs only, non-iOS, full-pipeline mode only. Skip entirely under--symbol-only: no release branch is required as input, and Branches-to-build is left untouched. Otherwise set Branches-to-build to the router-resolved release branch: planupdate <folder> <job> --branch <rel>. d. iOS jobs (UnityIOS/folder, branches likeios/release-*/*/release-ios-*) — add the define symbol ONLY, never change the branch; report that the iOS release branch does not yet contain the config (its own migration is a separate, unscheduled step). - Show the full before/after diff for every job about to change (symbols, branch, repo, any
CLOUDX removal) and get explicit confirmation (
AskUserQuestion) before any POST — this mutates shared CI config other people rely on. - On confirmation:
update <folder> <job> --set PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS='<new value>' [--branch <rel>] [--repo <url>]per job, batching every field that job needs in one call. - Verify independently —
verify <folder> <job> --expect PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS='<new value>' --expect-triggers yes. In full-pipeline mode only, also separatelyget-configto read the branch spec back fromconfig.xmland confirm it now reads the resolved release branch (skip this read-back under--symbol-only— the branch was never touched) — never trust theupdatecall’s own success as proof. - Report per-job result: repo URL (confirmed/switched), branch (before/after, Release only, full-pipeline mode only), define-symbols (already-present/appended, CLOUDX removed or not), push-trigger presence (full-pipeline mode only), and verified status.
Hard rules
Section titled “Hard rules”- Idempotency is exact-token, not substring. Split the
;-joined list and compare tokens directly;str.includes('X_FLOOR_PROBING')both over-matches (a symbol that merely contains the string) and risks under-matching on stray whitespace. - Append-only. This is not a full-string overwrite — never drop or reorder an existing token; a stale “before” read turned into a full replace can silently delete an unrelated project-specific symbol.
- Reuse
t1k-jenkins-job’s credential resolution — never mint or ask for a new Jenkins token if one is already resolvable via env or the registered MCP server. - Job class only matters for the push-trigger policy, not for the symbol — Develop AND Release
both get
X_FLOOR_PROBING; a Develop job’s stripped push trigger (pert1k-jenkins-job’s house policy) is unrelated and must be left alone. This skill only ADDS a trigger check — it never strips or adds a trigger itself. - Two Jenkins folders, two jobs each (Android: Develop/Release; iOS: Develop/Release) is the common case for a project shipping both platforms — do not stop after the first platform found.
- The Release job’s branch-to-build change happens BEFORE the router pushes (full-pipeline mode
only) — this skill never pushes anything itself; it only rewrites the job config so the push
(owned by the router) lands on a build spec that already expects the new branch. Under
--symbol-onlyno branch change happens at all, and the router never pushes in that mode either.
Executed by
Section titled “Executed by”Main session (inline), driving t1k-jenkins-job’s scripts/jenkins-job.cjs directly for
list/get-config/update/verify. This skill supplies only the idempotent-append DECISION
LOGIC (which token, which jobs, confirm-before-POST) — the config.xml mutation, credential
resolution, and independent verify machinery are t1k-jenkins-job’s, never duplicated here.
Related
Section titled “Related”t1k-jenkins-job— SSOT for config.xml mutation, credential resolution, verify-independent-of-writet1k-jenkins-unity— job-creation and define-symbol detection conventions (t1k-jenkins-unity/references/project-detection.md,t1k-jenkins-unity/references/param-matrix.md)t1k-unity-mobile-floor-probing-config— the config-asset half of this featuret1k-unity-mobile-floor-probing-pr— the git/PR halft1k-unity-mobile-floor-probing— the router; owns release-branch resolution (its step 5) and the push that starts the build (its step 7), both consumed here