Files
zeekayandHanzo Dev f746272ea4 ci: a runner label names the platform, not the org
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 Dev <[email protected]>
2026-09-08 12:09:46 -07:00

27 lines
903 B
YAML

name: Release
on:
push:
branches: [main]
workflow_dispatch: {}
concurrency:
group: release-git-runner
cancel-in-progress: false
jobs:
build:
runs-on: [linux-amd64]
timeout-minutes: 45
steps:
- uses: actions/checkout@v4
- name: Build + push ghcr.io/hanzoai/git-runner
env:
GH_TOKEN: ${{ secrets.MIRROR_GH_TOKEN }}
run: |
set -euo pipefail
echo "$GH_TOKEN" | docker login ghcr.io -u hanzo-dev --password-stdin
VER=0.6.1-hanzo.$(git rev-parse --short=7 HEAD)
# multi-target Dockerfile: dind is THE fleet image (s6 + dockerd +
# git-runner); a bare build ships the last stage (basic) — no docker.
docker build --target dind -t "ghcr.io/hanzoai/git-runner:${VER}" .
docker push "ghcr.io/hanzoai/git-runner:${VER}"
echo "pushed ghcr.io/hanzoai/git-runner:${VER}"