mirror of
https://github.com/hanzoai/tasks.git
synced 2026-10-04 02:04:03 +00:00
zeekayandHanzo Dev
914ba48887
git.hanzo.ai is canonical and reads .hanzo/workflows, so cicd.yml moves there by changing directory and nothing else — same GitHub Actions syntax, same runs-on, byte-identical file. .github/workflows keeps exactly one workflow, sync.yml, which carries pushed refs to the forge. hanzo.yml still holds all the config, so the build and test lanes are unchanged; it just points at the new path. LLM.md documents the chain and drops a stale reference to build-and-publish.yml, a workflow this repo no longer has. Co-authored-by: Hanzo Dev <[email protected]>
22 lines
846 B
YAML
22 lines
846 B
YAML
# Canonical CI/CD config for hanzoai/tasks — read by both the hanzoai/ci
|
|
# reusable workflow (.hanzo/workflows/cicd.yml) and platform.hanzo.ai
|
|
# (webhook → BuildScheduler → arcd → operator rollout). One file, one way.
|
|
#
|
|
# The image is the root Dockerfile: native ZAP-only tasksd (no CGO, no gRPC,
|
|
# no protobuf) with the admin SPA embedded from ui/dist (checked in;
|
|
# scripts/sync-admin-ui.sh refreshes it).
|
|
images:
|
|
- name: tasks
|
|
context: .
|
|
dockerfile: Dockerfile
|
|
repo: ghcr.io/hanzoai/tasks
|
|
|
|
# The engine + SDK suites are the repo's real gate (event-sourced durable
|
|
# core, schedule sweeper, dispatch, replay). -race matches how the suites
|
|
# are developed and how regressions have actually been caught.
|
|
test:
|
|
- name: go-test
|
|
run: go test -race ./pkg/... ./cmd/...
|
|
- name: go-vet
|
|
run: go vet ./pkg/... ./cmd/...
|