Skip to content

ci: move compatible Linux jobs to rajesh-gb-1 - #5

Open
aShanki wants to merge 3 commits into
masterfrom
rajesh/c7fafc44f3e5b95ec6f3
Open

aShanki wants to merge 3 commits into
masterfrom
rajesh/c7fafc44f3e5b95ec6f3

Conversation

@aShanki

@aShanki aShanki commented Oct 25, 2026 •

Copy link
Copy Markdown
Member

Summary

Existing Linux jobs → selected-repository org runner group → disposable rajesh-gb-1 container

Move this repository's selected compatible Linux jobs to the owned runner pool. Preserve every existing check, trigger, permission, artifact and deployment condition. Chromium OS libraries are baked into the image, so browser download steps run without root.

Evidence

  • Before: these jobs request GitHub-hosted Ubuntu compute.
  • After: the organization pool is registered online with the exact requested labels. Each job gets a clean container as UID 1001, no host mounts or Docker socket, all Linux capabilities dropped, and 3 CPU / 8 GiB limits.
  • YAML parsing, semantic comparison against the previous workflow, and git diff --check passed. Only selected Linux runner assignments changed; Windows, macOS, SDK-specific jobs and approval gates are unchanged.
  • The image smoke test passed for nonroot identity, writable toolcache, Maven/Java 21 and Paramiko. Repository CI results will be recorded before handoff where PR triggers exist. Main-only deployment/index-update flows have not been triggered from this unmerged branch.

Merge Danger

Door: two-way

Revert runner labels to return to hosted compute. This PR does not merge itself or bypass deployment approvals.

Blast Radius: CI

The pool has two concurrent Linux slots for flarialmc and one for flarialconsulting, each capped independently. Jobs queue when those slots are busy. The group is restricted to explicitly selected repositories. GitHub artifact/cache storage remains separately metered.

Change-Id: chg_5d85b172d260553d0237ff78

Observed verification

Traceability correction: the retained original runner-migration request is authoritative. Earlier unresolved dispatch-alias audit events remain preserved; this corrects the association without changing workflow behavior.

Additional compatible jobs prepared: verify, release-apk, publish. Parsed workflow comparison verifies unchanged triggers, job IDs, permissions, matrices, existing test/release commands and release conditions. Root package installation is replaced only where the image supplies the exact required tool. Publication/branch-update jobs were not triggered from the review branch. Runtime contract/build results are recorded before handoff.

Final owned-runner verification: verify passed (https://github.com/flarialmc/Launchly/actions/runs/40218944397/job/121246096744); dependency-review passed (https://github.com/flarialmc/Launchly/actions/runs/40218944397/job/121246096598); verify passed (https://github.com/flarialmc/Launchly/actions/runs/40218942242/job/121246090114); release-apk passed (https://github.com/flarialmc/Launchly/actions/runs/40218942242/job/121246089890). Publication/emulator conditions remain unchanged.

Preserve native platform jobs, test commands, required review checks and release gates.

Change-Id: chg_c0eaa68e16f9ad85d775c6b2
Correct the earlier dispatch alias association without changing workflow contents. Original audit events and commits remain retained.

Change-Id: chg_5d85b172d260553d0237ff78
Preserve test commands, triggers, permissions, matrix and release conditions. Use baked system packages without root job steps.

Change-Id: chg_5d85b172d260553d0237ff78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants