Skip to content

ci: route changes/validate jobs off the self-hosted runner pool #2507

Description

@JSONbored

Parent: #1936

Problem

The changes (path-filter) and validate (result-aggregation) jobs in .github/workflows/ci.yml are routed onto the self-hosted [self-hosted, gittensory] pool for same-repo PRs despite doing no build/test work, adding two more self-hosted slots per PR ahead of and after the one job that actually needs the VPS.

changes is just actions/checkout + git diff --check + dorny/paths-filter — it runs first and its own output decides whether validate-code needs to run at all, so gating it behind the same contended self-hosted queue it's meant to protect is circular (a busy self-hosted pool delays even discovering that a doc-only PR needs no heavy job). validate only reads needs.*.result and echoes a pass/fail message (2-minute timeout) yet still requests a self-hosted slot. Neither job touches node_modules, Docker, or anything the self-hosted VPS caching benefits.

Fix

Route changes and validate unconditionally to ubuntu-latest; only validate-code (the job that actually reuses the cached node_modules/toolchain) needs to stay on [self-hosted, gittensory].

Verification

  • Confirm current changes/validate job config against .github/workflows/ci.yml (line numbers may have shifted).
  • Open a test PR and confirm changes/validate now run on ubuntu-latest, validate-code still runs self-hosted, and the overall gate result is unchanged.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

Status
Done

Relationships

None yet

Development

No branches or pull requests

Issue actions