Commit 36fb411
authored
chore(ci): scenario tests pick docker registry by repo on v5-next (#24022)
## What
In `ci3.yml`'s `ci-network-scenario` job, select the Aztec docker image
registry based on the repository for release-tag runs, instead of
hardcoding `aztecprotocol/aztec:${tag}`:
- `AztecProtocol/aztec-packages-private` → `INTERNAL_DOCKER_REGISTRY`
(masked)
- everything else → `aztecprotocol` (public)
Also wires `INTERNAL_DOCKER_REGISTRY` into the step env.
## Why
The nightly Spartan scenario tests run on the **private** repo from
`v5.*` nightly tags (cut from `v5-next`), so the executing `ci3.yml` is
the one on `v5-next`. There it still pulled `aztecprotocol/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-internal` vs `deploy-staging-public`
(`use_internal_docker_registry`), and is a backport of the equivalent
change already on `next` (commit `01f1bc5e9a8`, "chore: deployments",
A-1163) that was not carried over to `v5-next`.
---
*Created by
[claudebox](https://claudebox.work/v2/sessions/e39ae8121349e17d) ·
group: `slackbot`*1 file changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
254 | 254 | | |
255 | 255 | | |
256 | 256 | | |
| 257 | + | |
257 | 258 | | |
258 | 259 | | |
259 | 260 | | |
| |||
269 | 270 | | |
270 | 271 | | |
271 | 272 | | |
272 | | - | |
| 273 | + | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
273 | 283 | | |
274 | 284 | | |
275 | 285 | | |
| |||
0 commit comments