ober/jerboa-android
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document CI runner locations: linux-amd64 runs on build@infra1 #10

Merged
ober merged 1 commit from docs/linux-runner-infra1 into main 2026-09-21 17:57:38 -04:00
Conversation 0 Commits 1 Files changed 4 +86 -2
ober commented 2026-09-21 17:50:12 -04:00
Owner
Copy link

What

Documentation for CI runner infrastructure, so the linux runner's location is never ambiguous again.

  • New docs/ci-runners.md — exactly where each CI label runs:
    • linux-amd64 → runner infra1-linux-amd64 on ssh build@infra1 (forgejo-runner v12.7.3 systemctl --user service under the build user, host mode, linger enabled). The android-sdk job runs here.
    • freebsd-amd64 → biggus jails (unchanged).
    • DECOMMISSIONED: the bhyve ubuntu-server VM on biggus (old runner buntu-linux-amd64, id 14). Registration deleted, ubuntu_server_vm_enable="NO" — never start it. A waiting linux-amd64 job means check build@infra1, not biggus.
  • Runner admin recipes (list runners, mint registration token via GET, re-register procedure).
  • README pointer.

Infra change this documents (already live)

infra1-linux-amd64 registered and running on build@infra1; old buntu runner deleted; bhyve VM stopped and disabled. This PR's own CI run is the end-to-end proof that android-sdk executes on infra1.

Version

0.1.7 → 0.1.8

## What Documentation for CI runner infrastructure, so the linux runner's location is never ambiguous again. - **New `docs/ci-runners.md`** — exactly where each CI label runs: - `linux-amd64` → runner `infra1-linux-amd64` on **`ssh build@infra1`** (forgejo-runner v12.7.3 `systemctl --user` service under the `build` user, host mode, linger enabled). The `android-sdk` job runs here. - `freebsd-amd64` → biggus jails (unchanged). - **DECOMMISSIONED**: the bhyve `ubuntu-server` VM on biggus (old runner `buntu-linux-amd64`, id 14). Registration deleted, `ubuntu_server_vm_enable="NO"` — never start it. A waiting `linux-amd64` job means check `build@infra1`, not biggus. - Runner admin recipes (list runners, mint registration token via GET, re-register procedure). - README pointer. ## Infra change this documents (already live) `infra1-linux-amd64` registered and running on build@infra1; old buntu runner deleted; bhyve VM stopped and disabled. This PR's own CI run is the end-to-end proof that android-sdk executes on infra1. ## Version 0.1.7 → 0.1.8
Document CI runner locations; linux-amd64 runs on build@infra1
All checks were successful
version-policy / required (pull_request) Successful in 3m43s
Details
required-ci / host-required (pull_request) Successful in 3m43s
Details
required-ci / android-sdk (pull_request) Successful in 5m24s
Details
6307e4d3e6 
The linux-amd64 Forgejo runner is infra1-linux-amd64 on ssh build@infra1
(forgejo-runner systemd --user service, host mode). The bhyve
ubuntu-server VM on biggus that used to host the buntu-linux-amd64
runner is decommissioned: registration deleted, rc script disabled.
Never start that VM; linux CI lives on infra1 only.
ober merged commit 86be126be7 into main 2026-09-21 17:57:38 -04:00
ober referenced this pull request from a commit 2026-09-21 17:57:40 -04:00
Merge pull request #10
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ober/jerboa-android!10
No description provided.