chore(ci3): remove the dashboard, the minio harness and the redis tooling - #25430
Closed
ludamad wants to merge 3 commits into
Closed
chore(ci3): remove the dashboard, the minio harness and the redis tooling#25430ludamad wants to merge 3 commits into
ludamad wants to merge 3 commits into
Conversation
ludamad
force-pushed
the
ad/ci3-remove-dashboard
branch
2 times, most recently
from
September 9, 2026 03:36
7f70999 to
8062322
Compare
ludamad
added this pull request to stack #25431
September 9, 2026 04:14
ludamad
force-pushed
the
ad/ci3-remove-dashboard
branch
from
September 9, 2026 15:47
8062322 to
8d9229b
Compare
ludamad
force-pushed
the
ad/ci3-remove-dashboard
branch
from
September 9, 2026 18:58
8d9229b to
9d67a4b
Compare
ludamad
force-pushed
the
ad/ci3-remove-dashboard
branch
from
September 9, 2026 18:59
9d67a4b to
48f5164
Compare
added 3 commits
September 9, 2026 17:51
Adds ci3/CI3_SERVER_API.md, the small HTTP API ci3 will use for logs, the test cache, run metadata, events and build-cache artifacts, together with: - ci3/ci3_client_*: the only way ci3 will talk to a server. No-ops when there is none. - ci3/source_ci3_client: discovery, configured by CI3_SERVER_URL (a URL, or `compat`), CI3_SERVER_TOKEN and CI3_PUBLIC_URL. A local run starts the file-backed server on demand. - ci3/ci3_server: two reference implementations. The file backend keeps everything under /tmp/ci3. The transitional compat backend forwards to the redis/S3 stores the current ci3 writes to directly, with the key shapes the labs dashboard reads, so CI keeps its logs and test cache until that dashboard serves the API itself. - tests for both backends (the compat one against a throwaway redis and a fake aws CLI). Nothing in ci3 uses any of this yet; the switch-over is the next PR.
Every ci3 script now reaches its stores only through the ci3_client_* scripts: 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, and cache_upload/download/exists/ls (artifact reads fall back to the public build cache). source_redis and source_cache are gone; ci3 no longer writes to S3 itself. bootstrap_ec2 hands the instance CI3_SERVER_URL as configured, or `compat` with none, so the instance runs the compat server and CI behaves as before; a developer's on-demand local server is never forwarded. Workflows forward CI3_SERVER_URL/CI3_SERVER_TOKEN; Post-Actions runs the compat server so the whole-run success marker still lands in the build cache; the release job downloads the packed release with aws directly. Also fixed on the way, found by running this in CI: the bb benchmark scripts sourced source_redis/source_cache, and make labs-use-local ran labs' bootstrap with the foundation's ci3 root exported.
…ling The CI dashboard (rkapp) lives in aztec-node, which is where the production implementation of ci3/CI3_SERVER_API.md will be built; nothing here reads redis any more. Removes ci3/dashboard, ci3/lua, watch_ci and ci.sh dash, the unused cache_delete and minio test harness, the bundled redis-cli, and the redis packages from the bootstrap dependencies. Docs describe the server API instead of redis.
ludamad
force-pushed
the
ad/ci3-remove-dashboard
branch
from
September 9, 2026 21:54
48f5164 to
d1d7727
Compare
Collaborator
Author
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.
Third of three (on the switch-over PR). With ci3 talking only to the server API, nothing here reads redis any more and the CI dashboard (rkapp) belongs in aztec-node, where the production implementation of
ci3/CI3_SERVER_API.mdwill be built.Removes
ci3/dashboard,ci3/lua,watch_ciandci.sh dash, the unusedcache_delete, the minio test harness (source_test), the bundledredis-cli, andredis-tools/redisfrom the bootstrap dependencies. Docs (CI.md, the benchmark-chonk skill) describe the server API instead of redis.