mirror of
https://github.com/hanzoai/dev.git
synced 2026-11-21 09:59:11 +00:00
A release took 109 minutes (v0.7.10): five builds shared one 8-CPU node, each job compiled cargo-zigbuild or cargo-xwin first, and version and publish cloned the engine's whole history. The builds now ask for xl-linux-amd64, a 32 vCPU node each. Measured on that pool with the pin and lock unmoved: version 4.1 min to 15 s, a job's setup 3-4 min to 50 s, a warm Build 58-87 min to 4.6-6.8 min, publish 6.9 min to 2 min. With codex-core and 28 crates above it rebuilt, Build is 18 minutes. - version and publish check out the tag's commit alone. - cargo-zigbuild and cargo-xwin are the projects' release binaries, pinned by sha256. zigbuild goes to ~/.cargo/bin, where cargo install put it: it names its linker wrapper by a hash of its own path, and sccache hashes that into every object. From anywhere else the first build found nothing in the cache and took 24 minutes. - The cache key leaves out the version and crates/, so a Dev-only release restores its own key exactly and saves nothing. The windows archive also carries the pruned LLVM and the xwin SDK. - hanzo-dev compiles sixteen codegen units wide (228 s to 187 s). - Packaging, the asset downloads and the npm platform packages run side by side, each waited for by its pid. - Only a tag, or the default branch resuming one, publishes. Concurrency is per ref. - scripts/ghapi.sh carries every call to GitHub: a non-2xx is never parsed, a rate-limited call is waited out (at most 10 minutes) and asked again, a 5xx is asked again, anything else fails naming the status and GitHub's message. A release makes about 66 calls, down from 89, and version stops early when fewer than 100 are left. - The npm step asks KMS again on an error.