Repository navigation
ci: run the jobs on the self-hosted xite-ci runners - #97
DJAscendance wants to merge 4 commits into
Conversation
GitHub does not start jobs on GitHub-hosted runners for this account (spending limit). Both jobs now use the runner group xite-ci (Proxmox VM, Ubuntu 24.04, no GPU). Job names and test commands do not change. - runs-on: group xite-ci, labels self-hosted, Linux, X64. - apt-get waits for the dpkg lock (two runners share the VM). Refs #96
MiniMax-M3.1-Flash QAFindings1. Critical: fork pull requests are still scheduled on the self-hosted runnerFile: The protection is implemented as a step: - name: Same-repository branch
if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name != github.repository
run: |
echo "::error::Fork pull requests do not run on the self-hosted runners."
exit 1This does not prevent the job from being assigned to More importantly, for Use a job-level condition or route fork PRs to a GitHub-hosted runner. For example: jobs:
test:
# Keep all actual execution away from self-hosted runners for fork PRs.
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
runs-on:
group: xite-ci
labels: [self-hosted, Linux, X64]If this job must remain a required check that fails for forks, add a separate GitHub-hosted job that fails for fork PRs, or use a conditional At minimum, the same repository check must be moved to the job level, not left as a step-level guard. 2. Medium: the
|
MiniMax review of #97: the PR job ran apt on a shared persistent VM. - System libraries: apt runs on GitHub-hosted runners only. On the VM a check fails the job when a package is not installed. - Remove the dpkg lock timeout; no PR job on the VM runs apt. The VM now gives each xite-ci runner its own unprivileged user, home and Rust toolchain, with no sudo, PrivateTmp and NoNewPrivileges. Refs #96
MiniMax review (untrusted PR code on persistent runners): - test: a fork PR fails at the first step, before checkout, so no fork code runs on the VM and the required check fails closed. - Review: runs only for a same-repository PR head. - checkout: persist-credentials: false, so PR code cannot read the job token from the git config.
|
Closed without merge. The repository is now public.
Normal PR CI stays on GitHub-hosted Linux runners. Trusted GPU tests need a separate design. |
Summary
GitHub does not start jobs on GitHub-hosted runners for this account (spending limit). This PR moves all jobs of the two workflows to the self-hosted runner group
xite-ci. The group is forX_ITE_RandCodeMirror_Ronly and accepts no public repository.Changes
runs-onof each job:group: xite-ci,labels: [self-hosted, Linux, X64]. 2 jobs in 2 workflows.apt-getwaits up to 300 s for the dpkg lock. Two runners share the VM.Unchanged
CM_EVIDENCEallow list, CodeMirror 5.65.21 reference step.permissionsand checkout settings.Runner environment
Proxmox VM
gh-runner: Ubuntu 24.04, 8 vCPU, 13.6 GB RAM, no swap, no GPU. Rust 1.95.0 with rustfmt, clippy and wasm32-unknown-unknown is preinstalled. Each runner service hasMemoryMax=11G. The first test uses one active runner.Validation
Ledger effect
None: CI process change, no REA entry.
Report location
~/Projects/cybertown/.reports/ci-self-hosted/2026-10-28-xite-ci/REPORT.md
Issue Reference
Refs #96