hanzoai/ci
2
0
Fork 0
mirror of https://github.com/hanzoai/ci.git synced 2026-10-20 15:28:05 +00:00
Code Issues Releases Activity

Post a delegated build to the door that exists
Hanzo CI/CD / cicd (push) Failing after 3m29s
CI/CD / gate (push) Failing after 6m33s

Browse Source 
cloud registers the build endpoint at /v1/build and nowhere else
(apps/platform/platform.go). The nested address this defaulted to
answers 404, so every delegated build failed on a reply naming no
address, which reads like an outage rather than a wrong door.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-09-10 21:38:57 -07:00
co-authored by Hanzo Dev
parent 549ec7fc63
commit cdadf74720
1 changed files with 17 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/build.yml
+17 -13
View File
@@ -1941,19 +1941,23 @@ jobs:
# the address that can answer.
if: inputs.mode == 'delegate'
env:
# The address the DEPLOYED cloud serves. /v1/build is where this is
# going — building is its own concept, not something platform owns —
# and it is already committed on cloud's side. Until that ships, a
# door that does not answer is worse than a nested name: every
# delegated build 404s and no repo can produce an image.
# The build door, reached as the SERVICE it is. The runner and cloud sit
# in the same cluster, and addressing the public host sent this request
# out to the edge, through a tunnel, and back to a pod one hop away —
# which is where it died: the ingress saw a 502 in 180ms and cloud
# logged the request not at all. A build should not leave the cluster to
# reach a service beside it. RUNNER_URL still overrides for anything
# running outside.
RUNNER_URL: ${{ vars.RUNNER_URL || 'http://cloud.hanzo.svc.cluster.local:8000/v1/platform/runner' }}
# `/v1/build`, FLAT, because building is its own service rather than
# something platform owns — cloud registers it there and at no other
# address (apps/platform/platform.go). The nested `/v1/platform/runner`
# this defaulted to answers 404, so every delegated build died on a
# reply that names no address and reads like an outage. Measured
# against the deployed cloud: `/v1/platform/runner` 404s, `/v1/build`
# takes the org's own machine identity and answers 400 for an empty
# body — the door, admitting the credential this step holds.
#
# Reached as the SERVICE it is. The runner and cloud sit in the same
# cluster, and addressing the public host sent this request out to the
# edge, through a tunnel, and back to a pod one hop away — which is
# where it died: the ingress saw a 502 in 180ms and cloud logged the
# request not at all. A build should not leave the cluster to reach a
# service beside it. RUNNER_URL still overrides for anything running
# outside.
RUNNER_URL: ${{ vars.RUNNER_URL || 'http://cloud.hanzo.svc.cluster.local:8000/v1/build' }}
# The version tag is WRITTEN by this job, onto the manifest the door
# pushed, so this lane needs the registry credential the buildx lane's
# login steps hold — and the registry read bin/imgver takes its