Files
zeekayandHanzo Dev d57e6c4082 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.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-06 02:30:55 -07:00

15 lines
592 B
YAML

# The app that proves the native PaaS path: git -> in-cluster BuildKit -> GHCR ->
# operator -> tenant ingress, calling api.hanzo.ai/v1 on every request.
#
# Two gates for the two ways it can break. The image build proves the Dockerfile
# still produces a runnable container; the Dockerfile only COPYs app.py and never
# runs python, so it cannot see a syntax error in the app — py_compile does.
images:
- name: paas-demo
context: .
dockerfile: Dockerfile
repo: ghcr.io/hanzoai/paas-demo
test:
- name: compile
run: python3 -m py_compile app.py && echo "app.py compiles"