chore(ci): scenario tests pick docker registry by repo on v5-next - #24022
Merged
Conversation
AztecBot
added
ci-draft
alexghr
approved these changes
Jun 11, 2026
AztecBot
added
ci-no-fail-fast
alexghr
marked this pull request as ready for review
June 11, 2026 14:54
alexghr
enabled auto-merge
June 11, 2026 14:54
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.
What
In
ci3.yml'sci-network-scenariojob, select the Aztec docker image registry based on the repository for release-tag runs, instead of hardcodingaztecprotocol/aztec:${tag}:AztecProtocol/aztec-packages-private→INTERNAL_DOCKER_REGISTRY(masked)aztecprotocol(public)Also wires
INTERNAL_DOCKER_REGISTRYinto the step env.Why
The nightly Spartan scenario tests run on the private repo from
v5.*nightly tags (cut fromv5-next), so the executingci3.ymlis the one onv5-next. There it still pulledaztecprotocol/aztec:${tag}from the public registry, which does not hold the private/internal image.This is the same public/private split already used for
deploy-staging-internalvsdeploy-staging-public(use_internal_docker_registry), and is a backport of the equivalent change already onnext(commit01f1bc5e9a8, "chore: deployments", A-1163) that was not carried over tov5-next.Created by claudebox · group:
slackbot