Files
engine/hanzo.yml
zeekay fdb0a12268 ci: canonical pair — hanzo.yml + forge caller
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.
2026-08-06 03:29:07 -07:00

31 lines
1.6 KiB
YAML

# Canonical CI/CD config for hanzoai/engine — read by the hanzoai/ci reusable
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# The Zen inference engine: a 23-crate Rust workspace.
#
# Test-only caller, deliberately. The image lane already exists and is not this
# one — .hanzo/workflows/deploy.yml builds Dockerfile and pushes it, and the
# GPU/FFI/release lanes sit beside it. Declaring `images:` here would run a
# second full release build of the same workspace (the Dockerfile compiles
# hanzo-server + hanzo-bench with CARGO_BUILD_JOBS=2) on every push, for an
# artifact that is already being produced. Two builds of one commit is not
# twice the truth; it is twice the runner.
#
# `rustup component add rustfmt` first: the toolchain this workflow provisions
# (dtolnay/rust-toolchain@stable) installs the compiler ALONE, so `cargo fmt`
# dies with "'cargo-fmt' is not installed for the toolchain" before reading a
# line of code — a red run that says nothing about the repo. ci.yml buys this
# with `components:` on the toolchain action; the provision step above is not
# ours to configure, so the gate buys it itself. It is idempotent.
#
# The gates are the repo's own (.hanzo/workflows/ci.yml), cheapest first: fmt
# is seconds and catches what needs no compiler, then a full type-check of every
# member. `cargo check` — not `cargo build` — because nothing here consumes a
# binary; the question this gate asks is whether the workspace still compiles.
test:
- name: fmt
run: rustup component add rustfmt && cargo fmt --all -- --check
- name: check
run: cargo check --workspace