Make buildkite push images with gcr.io at release pipeline.

GCR will be deprecated, while the prefix `gcr.io` will be
be hosted via Artifact Registry. By adding this one extra step,
all test images will be accessible via both `gcr.io` and
`pkg.dev`.

PiperOrigin-RevId: 694278137
This commit is contained in:
Jing Chen
2024-11-07 16:07:11 -08:00
committed by gVisor bot
parent c80684f5d9
commit 155cdcb458
2 changed files with 4 additions and 3 deletions
+2
View File
@@ -24,6 +24,7 @@ steps:
if: build.branch == "master" && build.tag == null
commands:
- make ARCH=x86_64 DOCKER_PUSH_AS_LATEST=true push-all-images
- make ARCH=x86_64 REMOTE_IMAGE_PREFIX=gcr.io/gvisor-presubmit DOCKER_PUSH_AS_LATEST=true push-all-images
agents:
arch: "amd64"
- <<: *common
@@ -31,6 +32,7 @@ steps:
if: build.branch == "master" && build.tag == null
commands:
- make ARCH=aarch64 DOCKER_PUSH_AS_LATEST=true push-all-images
- make ARCH=aarch64 REMOTE_IMAGE_PREFIX=gcr.io/gvisor-presubmit DOCKER_PUSH_AS_LATEST=true push-all-images
agents:
arch: "arm64"
- <<: *common
+2 -3
View File
@@ -52,9 +52,8 @@ if available.
## Building and pushing images
All images can be built manually by running `build-<image>` and pushed using
`push-<image>`. Note that you can also use `build-all-images` and
`push-all-images`. Note that pushing will require appropriate permissions in the
project.
`push-<image>`. Note that you can also use `push-all-images`. Note that pushing
will require appropriate permissions in the project.
The continuous integration system can either take fine-grained dependencies on
individual `push` targets, or ensure all images are up-to-date with a single