mirror of
https://github.com/hanzoai/functions.git
synced 2026-10-30 15:04:37 +00:00
zeekayandHanzo Dev
f9bcc31f05
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]>
23 lines
1017 B
YAML
23 lines
1017 B
YAML
# hanzoai/functions — the serverless-function control plane (Go, Fission fork:
|
|
# controller, executor, router, CRDs).
|
|
#
|
|
# Gate only, no `images:`. Its many images are cut by the release lane
|
|
# (goreleaser + skaffold); one artifact, one producer.
|
|
#
|
|
# COMPILE AND VET, NOT the repo's `make test-run`. That target runs
|
|
# hack/runtests.sh, which provisions KUBEBUILDER_ASSETS via setup-envtest and
|
|
# talks to a KUBECONFIG — it needs a cluster, and the repo's own push_pr.yaml
|
|
# stands up kind before it can run. A gate that requires a cluster fails for the
|
|
# absence of a cluster, which says nothing about the commit.
|
|
#
|
|
# `go build ./...` still compiles every controller, informer and generated CRD
|
|
# client in the root module, and `go vet` catches what compiles but is wrong.
|
|
# test/tests/websocket is its own module and is deliberately out of scope of
|
|
# ./... — it is an end-to-end fixture, exercised by the kind lane.
|
|
test:
|
|
- name: build-and-vet
|
|
run: |
|
|
set -e
|
|
go build ./...
|
|
go vet ./...
|