Files
zeekayandHanzo Dev 0e85bad781 ci: fix the gate to assert the code, not the runner image
kv named the wrong server binary (kv-server, not valkey-server) and assumed a C
compiler the reusable installs only for Go callers; forum assumed a ruby the
reusable never provisions; rocm-rs left gpu-sort on, whose nested nightly
build-std step no stock runner can do; insights-rs asked for --all-features,
which selects the live-endpoint e2e feature.

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

25 lines
1.1 KiB
YAML

# hanzoai/kv — the Valkey-derived key/value server. C, built with make.
#
# Gate only. The image is already built and pushed by the native builder in this
# repo (.hanzo/workflows/deploy.yml → ghcr.io/hanzoai/kv), so declaring `images:`
# here would publish a second copy of the same commit under a different tag.
# What was missing is proof the source compiles, which is exactly what a C repo
# needs and had none of.
#
# The compiler provision is part of the assertion, not setup around it: the
# reusable installs gcc only for Go callers (it keys on go.mod), and this repo is
# C, so without it the gate would be reporting on the runner image instead of on
# the code. `make` builds deps/ (jemalloc, lua, fpconv, hdr_histogram) first, so
# a broken vendored dep fails here too. The version probe is the proof the link
# step actually produced a server, not just object files.
test:
- name: build
run: |
set -euo pipefail
command -v cc > /dev/null 2>&1 || {
sudo apt-get update -qq
sudo apt-get install -y -qq build-essential
}
make -j"$(nproc)"
./src/kv-server --version