Skip to content

t1k:unity:mobile:floor-probing-jenkins

FieldValue
Modulemobile
Version3.65.6
Effortmedium
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

/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_PROBING to PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS on 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 stale CLOUDX symbol.
  • 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-only mode: 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-job SKILL.md — credential resolution order (env → registered Jenkins MCP → ask), list / get-config / update / verify commands, the missing-<defaultValue>-element gotcha, and “never verify with the same helper you wrote with.”
  • t1k-jenkins-unity/references/project-detection.md and t1k-jenkins-unity/references/param-matrix.md — how PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS is read per platform (Android: / iPhone: keys) and the Develop/Release/Creative job-class conventions.
  1. Detect platforms — does the repo have a UnityAndroid/ and/or UnityIOS/ Jenkins folder (per t1k-jenkins-unity’s folder convention)? Use whichever exist; ask if ambiguous or neither is found.
  2. 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-config it and read back the git repo URL — job names don’t always match the project (LifeChoices repo → job LifeChoice-Release; TrickyChibi3-Release actually builds repo TrickyMonster).
    • Repo URL mismatch (observed: RoleSwapSprunky-Release still built repo RoleSwapEmotion on branch sprunky/release-1.0.8) → AskUserQuestion whether to switch it now (update <folder> <job> --repo <url>) before continuing, or skip this job.
  3. 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 read config.xml for com.cloudbees.jenkins.GitHubPushTrigger)? A --symbol-only call no longer means “no push is ever planned” — the router’s mode 3 uses --symbol-only for 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 — AskUserQuestion whether 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.
  4. For each (folder, job) pair, get-config and read the CURRENT PARAM_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 of X_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. Stale CLOUDX (Android jobs on a migrated GDK that now prefers AppLovin) — if the define-symbol string still carries a CLOUDX token, AskUserQuestion whether 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: plan update <folder> <job> --branch <rel>. d. iOS jobs (UnityIOS/ folder, branches like ios/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).
  5. 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.
  6. 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.
  7. Verify independently — verify <folder> <job> --expect PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS='<new value>' --expect-triggers yes. In full-pipeline mode only, also separately get-config to read the branch spec back from config.xml and confirm it now reads the resolved release branch (skip this read-back under --symbol-only — the branch was never touched) — never trust the update call’s own success as proof.
  8. 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.
  • 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 (per t1k-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-only no branch change happens at all, and the router never pushes in that mode either.

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.

  • t1k-jenkins-job — SSOT for config.xml mutation, credential resolution, verify-independent-of-write
  • t1k-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 feature
  • t1k-unity-mobile-floor-probing-pr — the git/PR half
  • t1k-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