From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PULL 1/7] gitlab: explicitly reference the upstream registry
Date: Tue, 25 May 2021 12:24:25 +0100 [thread overview]
Message-ID: <20210525112431.22005-2-alex.bennee@linaro.org> (raw)
In-Reply-To: <20210525112431.22005-1-alex.bennee@linaro.org>
Since c8e6793903 ("containers.yml: build with docker.py tooling") we
don't need to manually pull stuff from the upstream repository. Just
set the -r field to explicitly use that rather than the current
registry.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20210520174303.12310-3-alex.bennee@linaro.org>
diff --git a/.gitlab-ci.d/containers.yml b/.gitlab-ci.d/containers.yml
index 765408ae27..3fb3c14f06 100644
--- a/.gitlab-ci.d/containers.yml
+++ b/.gitlab-ci.d/containers.yml
@@ -12,10 +12,9 @@
script:
- echo "TAG:$TAG"
- echo "COMMON_TAG:$COMMON_TAG"
- - docker pull "$TAG" || docker pull "$COMMON_TAG" || true
- ./tests/docker/docker.py --engine docker build
-t "qemu/$NAME" -f "tests/docker/dockerfiles/$NAME.docker"
- -r $CI_REGISTRY_IMAGE
+ -r $CI_REGISTRY/qemu-project/qemu
- docker tag "qemu/$NAME" "$TAG"
- docker push "$TAG"
after_script:
--
2.20.1
next prev parent reply other threads:[~2021-05-25 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 11:24 [PULL 0/7] testing, gdbstub and plugin updates Alex Bennée
2021-05-25 11:24 ` Alex Bennée [this message]
2021-05-25 11:24 ` [PULL 2/7] gitlab: add special rule for the hexagon container Alex Bennée
2021-05-25 11:24 ` [PULL 3/7] gdbstub: Constify GdbCmdParseEntry Alex Bennée
2021-05-25 11:24 ` [PULL 4/7] gdbstub: Replace GdbCmdContext with plain g_array() Alex Bennée
2021-05-25 11:24 ` [PULL 5/7] hmp-commands: expand type of icount to "l" in replay commands Alex Bennée
2021-05-25 11:24 ` [PULL 6/7] gdbstub: tidy away reverse debugging check into function Alex Bennée
2021-05-25 11:24 ` [PULL 7/7] plugins/syscall: Added a table-like summary output Alex Bennée
2021-05-25 12:28 ` [PULL 0/7] testing, gdbstub and plugin updates Philippe Mathieu-Daudé
2021-05-25 15:05 ` Alex Bennée
2021-05-25 15:15 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210525112431.22005-2-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).