BFE EngineeringandClaude Fable 5
5155224594
Preparing the repo to go public (ADR-0007): - CI: kernel-build moves from the self-hosted runner to ubuntu-latest (installs its own cross toolchain + qemu, caches the pristine tarball). On a public repo a registered self-hosted runner is reachable from approved fork-PR workflows — i.e. arbitrary code on private infrastructure — and the build never actually needed the SDK host. ADR-0004 marked superseded-in-part; docs/ci-cd.md rewritten (site specifics now live only in the private deployment log). - Licensing: LICENSE gains the GPL-2.0 carve-out for patches/ and the kernel source excerpts (Linux derivatives; per-driver provenance was already tracked in PROVENANCE.md); patches/README.md states it too. - Scrubbed from the tip: bench-unit dev credentials and its gadget IP (m2-boot notes), the site AP SSID+BSSID and a neighboring AP's BSSID and the device WLAN MAC (wifi bring-up evidence — BSSIDs are geolocatable), the runner mesh IP. NOTE: these remain in git history; decision on a pre-publication history rewrite is separate. - Emoji cleanup across 21 tracked files (kernel port docs, review report, enforce-mcdc.sh) per repo text conventions: status marks became [x]/[wip]/[ ]/OK plain text. - "[maintainer]-gated" process phrasing normalized to "maintainer-gated" (attributions in dated evidence docs kept). Verified: zero emojis tracked; scrub grep clean; patches carry no internal references; ci.yml parses; shellcheck unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018HUayid7W5w7jBdb9Rrj1K
24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# ADR 0004 — CI/CD runner: 3rd repo-scoped self-hosted runner on 0640
|
|
|
|
**Status:** Superseded in part by ADR-0007 (2026-08-30) — `kernel-build` moved
|
|
to GitHub-hosted runners for the public repo and the self-hosted registration
|
|
is retired. Original decision below, kept for the record. (2026-08-25.)
|
|
|
|
## Context
|
|
The heavy kernel/firmware build needs the SDK toolchain and Buildroot's baked-in
|
|
absolute paths — impractical on GitHub-hosted runners. flare-edge already builds on
|
|
a repo-scoped self-hosted runner on `bfe-mpc-0640` (label `flare-edge`); a repo-scoped
|
|
registration cannot be shared across repos by label alone.
|
|
|
|
## Decision
|
|
Register a **third repo-scoped runner instance** on `bfe-mpc-0640`, label
|
|
`warden-sdk` (own systemd unit `actions.runner.bfe-noah-warden-sdk.*`, own
|
|
`CPUQuota=400%`/`MemoryMax=6G` drop-in). Only the heavy `kernel-build` job uses
|
|
`runs-on: [self-hosted, warden-sdk]`; all host-testable jobs (tests, coverage, MC/DC,
|
|
benchmarks, badges, patches-apply) run on GitHub-hosted runners.
|
|
|
|
## Consequences
|
|
- Isolated from the flare backend + flare-edge CI already on that host (cgroup-capped).
|
|
- Runner setup + host build deps + the project-local `python` venv documented in
|
|
`docs/ci-cd.md`, mirroring flare-edge's.
|