ci: a runner label names the platform, not the org
CI/CD / render (push) Failing after 0s
CI/CD / render (push) Failing after 0s
hanzo-build-linux-amd64, lux-build-linux-amd64, zoo-build-linux-amd64 and every other org-prefixed spelling all meant the same machine. Which org a job belongs to does not change which host can build it, so the org bought one pool name per org per arch and each could go stale on its own -- the evo host alone answered to fourteen names for one label. One vocabulary now: linux-amd64, linux-arm64, macos-arm64, win-amd64. The generic labels every plain workflow uses (ubuntu-latest, self-hosted) are untouched, so naive CI keeps working. Co-authored-by: Hanzo AI <[email protected]>
This commit is contained in:
@@ -19,7 +19,7 @@ on:
|
||||
|
||||
jobs:
|
||||
render:
|
||||
runs-on: [self-hosted, hanzo-build-linux-amd64]
|
||||
runs-on: [self-hosted, linux-amd64]
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
|
||||
|
||||
Reference in New Issue
Block a user