From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, "Thomas Huth" <thuth@redhat.com>,
berrange@redhat.com, f4bug@amsat.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <willianr@redhat.com>,
stefanha@redhat.com, crosa@redhat.com, pbonzini@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>,
aurelien@aurel32.net
Subject: [PATCH v1 2/8] gitlab: explicitly reference the upstream registry
Date: Thu, 20 May 2021 18:42:57 +0100 [thread overview]
Message-ID: <20210520174303.12310-3-alex.bennee@linaro.org> (raw)
In-Reply-To: <20210520174303.12310-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>
---
.gitlab-ci.d/containers.yml | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
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-20 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 17:42 [PATCH v1 0/8] various misc fixes (gitlab, gdbstub, plugins) Alex Bennée
2021-05-20 17:42 ` [PATCH v1 1/8] tests/tcg: add a multiarch signals test to stress test signal delivery Alex Bennée
2021-05-24 21:05 ` Richard Henderson
2021-05-20 17:42 ` Alex Bennée [this message]
2021-05-24 19:15 ` [PATCH v1 2/8] gitlab: explicitly reference the upstream registry Willian Rampazzo
2021-05-25 4:04 ` Philippe Mathieu-Daudé
2021-05-20 17:42 ` [PATCH v1 3/8] gitlab: add special rule for the hexagon container Alex Bennée
2021-05-25 3:54 ` Philippe Mathieu-Daudé
2021-05-25 9:40 ` Philippe Mathieu-Daudé
2021-05-25 11:25 ` Philippe Mathieu-Daudé
2021-05-25 15:06 ` Alex Bennée
2021-05-20 17:42 ` [PATCH v1 4/8] gdbstub: Constify GdbCmdParseEntry Alex Bennée
2021-05-24 21:06 ` Richard Henderson
2021-05-20 17:43 ` [PATCH v1 5/8] gdbstub: Replace GdbCmdContext with plain g_array() Alex Bennée
2021-05-20 17:43 ` [PATCH v1 6/8] hmp-commands: expand type of icount to "l" in replay commands Alex Bennée
2021-05-25 3:55 ` Philippe Mathieu-Daudé
2021-05-20 17:43 ` [PATCH v1 7/8] gdbstub: tidy away reverse debugging check into function Alex Bennée
2021-05-24 21:08 ` Richard Henderson
2021-05-25 3:57 ` Philippe Mathieu-Daudé
2021-05-20 17:43 ` [PATCH v1 8/8] plugins/syscall: Added a table-like summary output Alex Bennée
2021-05-24 17:50 ` [PATCH v1 0/8] various misc fixes (gitlab, gdbstub, plugins) Alex Bennée
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=20210520174303.12310-3-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).