Skip to content

ci: run workflows on self-hosted ARC pool (hanzo-build-linux-amd64/deploy)#2

Open
hanzo-dev wants to merge 1 commit into
mainfrom
ci/arc-runners
Open

ci: run workflows on self-hosted ARC pool (hanzo-build-linux-amd64/deploy)#2
hanzo-dev wants to merge 1 commit into
mainfrom
ci/arc-runners

Conversation

@hanzo-dev

Copy link
Copy Markdown
Member

CI: run on self-hosted ARC pool, not GitHub-hosted

Part of the org-wide sweep moving every hanzoai/* workflow off GitHub-hosted
runners onto our self-hosted Actions Runner Controller (ARC) scale sets on the
hanzo-k8s DOKS cluster.

Runner pools (hanzoai org):

  • hanzo-build-linux-amd64 — x86 builds
  • hanzo-deploy-linux-amd64 — kubectl deploys

Per org policy, hanzoai/* workflows must runs-on the hanzo pools only — no
cross-org runner sharing (a cross-org runs-on queues silently and cancels at
the 24h timeout). amd64-only is the canonical build path while DOKS has no arm64
droplets.

This branch was pushed during the bulk sweep but never had a PR opened; this PR
backfills it. Single commit:
ci: run on self-hosted ARC pool (hanzo-build-linux-amd64/deploy), not GitHub-hosted

@hanzo-dev

Copy link
Copy Markdown
Member Author

Conflicts with main: the workflow file(s) this ARC-pool migration edits have already diverged on main, so the runs-on: hanzo-build-linux-amd64 swap can't apply cleanly. Needs a rebase to re-resolve. Skipping in the PR sweep — reopen-ready once rebased.

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.

1 participant