mirror of
https://github.com/hanzo-cpp/sdk.git
synced 2026-11-20 19:55:32 +00:00
Hanzo CI/CD / test (linux-amd64) (push) Skipped
Hanzo CI/CD / test (linux-arm64) (push) Skipped
Hanzo CI/CD / test-advisory (push) Skipped
Hanzo CI/CD / test-amd64 (push) Failing after 1h14m46s
CI/CD / cicd (push) Failing after 1h14m48s
Hanzo CI/CD / cicd (push) Skipped
Hanzo CI/CD / verify (push) Skipped
71 lines
3.4 KiB
YAML
71 lines
3.4 KiB
YAML
# Hanzo CI — the ONE way this repo is gated, read by hanzoai/ci.
|
|
#
|
|
# No `images:` and no `deploy:`: this is a C++ client library. A consumer gets it
|
|
# from a tag via FetchContent or from a release archive, so what CI owes is a
|
|
# gate plus an artifact, not a running service.
|
|
#
|
|
# UNEXERCISED, and that is a fact about the fleet rather than about this file.
|
|
# Both runs on this repo so far are `completed / startup_failure` with ZERO jobs
|
|
# created — GitHub never scheduled one — while the same workflow on the hanzoai/*
|
|
# repos sits `queued` forever against `hanzo-build-linux-amd64`, an arc pool with
|
|
# zero registered runners. Actions is enabled and unrestricted on the org, so
|
|
# neither is a permissions gap. Every gate below is therefore verified by a
|
|
# clean-clone local build, and the numbers in LLM.md are that build's.
|
|
|
|
test:
|
|
- name: cmake-build
|
|
# ~2400 translation units in one static library. A regeneration that does not
|
|
# compile must not reach a tag, which is the whole reason this is a gate and
|
|
# not a README instruction.
|
|
run: |
|
|
set -e
|
|
cmake -B build -DCMAKE_BUILD_TYPE=Release
|
|
cmake --build build -j"$(nproc)"
|
|
|
|
- name: examples-build
|
|
# The six canonical flows, compiled against the client they demonstrate. An
|
|
# example that does not compile is worse than no example, so they are gated
|
|
# rather than merely committed.
|
|
run: |
|
|
set -e
|
|
cmake -B build -DHANZO_BUILD_EXAMPLES=ON
|
|
cmake --build build -j"$(nproc)" --target hello chat money store agent tools
|
|
|
|
binaries:
|
|
# C++ has no registry. The published artifact is a tagged GitHub release
|
|
# carrying the headers and the built library — built on every push so a break
|
|
# is caught immediately, published only on a tag.
|
|
- name: hanzo-cpp-sdk
|
|
run: |
|
|
set -e
|
|
cmake -B build -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=dist
|
|
cmake --build build -j"$(nproc)" --target install
|
|
tar -czf hanzo-cpp-sdk-"$(uname -m)"-linux.tar.gz -C dist .
|
|
out: hanzo-cpp-sdk-*.tar.gz
|
|
|
|
# THE CLIENT LANE — this repo is a PROJECTION of one API document at one version.
|
|
#
|
|
# hanzoai/cloud's release sends `repository_dispatch: spec-update` carrying
|
|
# (version, sha, spec_sha256); hanzoai/ci fetches openapi.yaml AT THAT SHA,
|
|
# REFUSES if the bytes hash to anything else, runs `generate:`, writes
|
|
# `.spec-lock` beside the code, and — only after the `test:` block below has
|
|
# passed over exactly those bytes — commits and cuts a patch.
|
|
#
|
|
# The document is hanzoai/cloud's `openapi.yaml` — emitted from the code by each
|
|
# app's own router and gated on every cloud release — and scripts/generate.sh now
|
|
# reads it, which it did not when this note was written. It read hanzoai/openapi's
|
|
# `hanzo.yaml` at branch `main` with no lock, so this lane and the script named
|
|
# two different documents. They name one now: `.spec-lock`, by commit.
|
|
#
|
|
# Measured at that commit, cloud's document is the LARGER of the two as well as
|
|
# the emitted one: 1814 paths / 2479 operations against hanzo.yaml's 1794 / 2456,
|
|
# a strict superset of its routes.
|
|
client:
|
|
# WHICH cloud, said out loud: hanzoai/ci defaults to `hanzoai/cloud`, which is
|
|
# the re-rooted OSS core and carries no openapi.yaml. The product line is what
|
|
# this SDK is a projection of. Keep equal to `.spec-lock`'s repo= line.
|
|
spec:
|
|
repo: hanzo-inc/cloud
|
|
generate: ./scripts/generate.sh
|
|
version: "CMakeLists.txt:grep -m1 -oE 'VERSION [0-9]+\\.[0-9]+\\.[0-9]+' CMakeLists.txt | cut -d' ' -f2"
|