chore: stop auto-deploying the ci3 dashboard from aztec-packages - #25293
Open
charlielye wants to merge 1 commit into
Open
chore: stop auto-deploying the ci3 dashboard from aztec-packages#25293charlielye wants to merge 1 commit into
charlielye wants to merge 1 commit into
Conversation
The dashboard runs on one shared box (ci.aztec-labs.com) but was vendored and auto-deployed from both aztec-packages (push to next) and aztec-node. Same target, last-writer-wins — so aztec-packages' copy silently overwrote aztec-node's. Remove the aztec-packages deploy workflow; the dashboard is now deployed manually from aztec-node (its workflow_dispatch), which carries the multi-org / TLS work. Longer term the dashboard should live in one place.
charlielye
enabled auto-merge
August 24, 2026 12:28
fcarreiro
approved these changes
Aug 24, 2026
charlielye
changed the title
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 24, 2026
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
2 participants
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.
The ci3 dashboard (rkapp on ci.aztec-labs.com) is a single shared service, but it was vendored and deployed from two repos:
nexttouchingci3/dashboard/**(added in58dc521480).workflow_dispatchonly).Both run the identical
deploy.sh→ rsync to the sameci.aztec-labs.com:rkandsystemctl restart rkapp. Same target, last-writer-wins — so aztec-packages' auto-deploy silently overwrote whatever aztec-node deployed, and aztec-node's copy (which now carries the multi-org dashboard sections + TLS/compose work) never stuck.This removes the aztec-packages deploy workflow. The dashboard is deployed manually from aztec-node for now (its
workflow_dispatch), which owns the current dashboard code. Longer term the dashboard should live in one place rather than be vendored into two product repos.No effect on any other CI: this only deletes a deploy workflow.