refactor(ci3): logs, test cache and artifacts through a server API - #25427
Open
ludamad wants to merge 1 commit into
Open
refactor(ci3): logs, test cache and artifacts through a server API#25427ludamad wants to merge 1 commit into
ludamad wants to merge 1 commit into
Conversation
ludamad
force-pushed
the
ad/ci3-client-server
branch
2 times, most recently
from
September 9, 2026 02:48
773bc53 to
b0ed9fa
Compare
ludamad
changed the title
ludamad
force-pushed
the
ad/ci3-client-server
branch
from
September 9, 2026 03:30
b0ed9fa to
f0fd5c6
Compare
ludamad
added this pull request to stack #25431
September 9, 2026 04:14
ludamad
force-pushed
the
ad/ci3-client-server
branch
4 times, most recently
from
September 9, 2026 22:37
96a21be to
0fcc6fc
Compare
ludamad
changed the title
ludamad
force-pushed
the
ad/ci3-client-server
branch
from
September 9, 2026 22:40
0fcc6fc to
effb313
Compare
ludamad
force-pushed
the
ad/ci3-client-server
branch
3 times, most recently
from
September 10, 2026 01:49
a64ded2 to
b2176a9
Compare
ludamad
force-pushed
the
ad/ci3-client-server
branch
2 times, most recently
from
September 10, 2026 02:46
8825f88 to
8f47016
Compare
ci3 no longer knows about redis, the S3 log bucket or the dashboard. Everything it stores goes through the HTTP API in ci3/CI3_SERVER_API.md via `ci3_client <command>`, which reads one file, ~/.ci3/config.json, written by ci3_setup: - local mode (the default): ci3_server, the file-backed reference server, on this machine. - aztec mode (CI3_PASSWORD in the environment, or CI): the labs CI dashboard at ci.aztec-labs.com, where CI logs live, behind its basic auth. The labs patch in labs-patches/0014 (aztec-node#140) makes the dashboard (rkapp) serve the API. The entry points (bootstrap.sh, ci.sh, the CI launcher, Post-Actions) run ci3_setup before ci3 loads. An existing config is honoured; a non-interactive run whose environment asks for the aztec server while the config says otherwise stops with an error, a terminal is asked. Rewired: cache_log, denoise, run_test_cmd, filter_cached_test_cmd, exec_test (per-test timings), log_ci_run, the Slack notifiers, ci.sh log/test-timings, cache_upload/download/ exists/ls (artifact reads fall back to the public build cache; ci3 never writes to S3 itself), bench_compare, docker_isolate, the bb benchmark breakdown uploads. source_redis and source_cache are gone. The release job downloads the packed release with aws directly. Also fixed on the way, found in CI: the bb benchmark scripts sourced source_redis, and make labs-use-local ran labs' bootstrap with the foundation's ci3 root exported.
ludamad
force-pushed
the
ad/ci3-client-server
branch
from
September 10, 2026 03:34
8f47016 to
06443b5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First of two (#25429 deletes what this makes obsolete). ci3 no longer knows about redis, S3 logs or the dashboard: everything it stores goes through the HTTP API in
ci3/CI3_SERVER_API.md, viaci3_client <command>, which reads only~/.ci3/config.json.ci3_setupwrites that config once and starts the server it names. Local:ci3_server, file-backed, no auth.CI=1orCI3_PASSWORDset: the labs dashboard atci.aztec-labs.com, behind its basic auth, made to serve the API bylabs-patches/0014(feat(ci3): the dashboard serves the ci3 server API aztec-labs-eng/aztec-node#140).cache_log,denoise,run_test_cmd,filter_cached_test_cmd,exec_test(timings),log_ci_run, notifiers,ci.sh log/test-timings,cache_*(public build cache as read fallback),bench_compare,docker_isolate, bb bench uploads, Post-Actions.source_redis/source_cacheand theci:test:*pub/sub events are gone.Merge after aztec-node#140 is deployed with
DASHBOARD_PASSWORDset and theCI3_PASSWORDsecret matching it. Until then a run on this branch still passes but without logs or test cache (the client finds no API and disables both).Tests:
ci3/tests/ci3_client_test(65) andci3/tests/ci3_rkapp_test(23: the patched dashboard under gunicorn on a throwaway redis and minio, driven by the real ci3 scripts, plus the patch's own unit suite). Reviewed by Claude, Codex and Greptile. Fullci-fullbuilds ran through the patched dashboard on the build instance (runs 34427053489, 34430726504) before the interim launcher was removed.