From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Alessandro Di Federico <ale.qemu@rev.ng>
Cc: Alessandro Di Federico <ale@rev.ng>,
bcain@quicinc.com, richard.henderson@linaro.org,
qemu-devel@nongnu.org, babush@rev.ng, tsimpson@quicinc.com,
nizzo@rev.ng, philmd@redhat.com
Subject: Re: [PATCH v5 14/14] gitlab-ci: do not use qemu-project Docker registry
Date: Tue, 29 Jun 2021 15:37:21 +0100 [thread overview]
Message-ID: <YNswId7vQL/zYJCR@redhat.com> (raw)
In-Reply-To: <20210619093713.1845446-15-ale.qemu@rev.ng>
On Sat, Jun 19, 2021 at 11:37:13AM +0200, Alessandro Di Federico via wrote:
> From: Alessandro Di Federico <ale@rev.ng>
>
> This commit is necessary in order to use container built by the current
> run of the CI. If we don't do this, we use official containers which are
> not affected by the additional dependencies we're introducing.
>
> Signed-off-by: Alessandro Di Federico <ale@rev.ng>
> ---
> .gitlab-ci.d/container-cross.yml | 2 +-
> .gitlab-ci.d/container-template.yml | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/.gitlab-ci.d/container-cross.yml b/.gitlab-ci.d/container-cross.yml
> index 0fcebe363a..eb134e927d 100644
> --- a/.gitlab-ci.d/container-cross.yml
> +++ b/.gitlab-ci.d/container-cross.yml
> @@ -63,7 +63,7 @@ hexagon-cross-container:
> - docker:dind
> before_script:
> - export TAG="$CI_REGISTRY_IMAGE/qemu/$NAME:latest"
> - - export COMMON_TAG="$CI_REGISTRY/qemu-project/qemu/qemu/$NAME:latest"
> + - export COMMON_TAG="$CI_REGISTRY_IMAGE/qemu/$NAME:latest"
This isn't right.
We have either one or two images. If this is a new user fork,
we only have the $COMMON_TAG image in the main QEMU registry.
If this is a existing fork, we might have two images, one in
the main QEMU registry and one in the user's fork registry.
Both of the images are to be used as a cache source, with
the container tools figuring out which has matching image
layers, if any.
This proposed change makes TAG and COMMON_TAG identical
which means we loose inheritance from the main QEMU
registry, which almost always has suitable cached content.
> - docker info
> - docker login $CI_REGISTRY -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD"
> script:
> diff --git a/.gitlab-ci.d/container-template.yml b/.gitlab-ci.d/container-template.yml
> index 1baecd9460..c85ae377b8 100644
> --- a/.gitlab-ci.d/container-template.yml
> +++ b/.gitlab-ci.d/container-template.yml
> @@ -5,7 +5,7 @@
> - docker:dind
> before_script:
> - export TAG="$CI_REGISTRY_IMAGE/qemu/$NAME:latest"
> - - export COMMON_TAG="$CI_REGISTRY/qemu-project/qemu/$NAME:latest"
> + - export COMMON_TAG="$CI_REGISTRY_IMAGE/qemu/$NAME:latest"
> - apk add python3
> - docker info
> - docker login $CI_REGISTRY -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD"
Again this is wrong.
> @@ -14,7 +14,7 @@
> - echo "COMMON_TAG:$COMMON_TAG"
> - ./tests/docker/docker.py --engine docker build
> -t "qemu/$NAME" -f "tests/docker/dockerfiles/$NAME.docker"
> - -r $CI_REGISTRY/qemu-project/qemu
> + -r $CI_REGISTRY_IMAGE
I'm not sure about this one though.
> - docker tag "qemu/$NAME" "$TAG"
> - docker push "$TAG"
> after_script:
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-06-29 14:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 9:36 [PATCH v5 00/14] target/hexagon: introduce idef-parser Alessandro Di Federico via
2021-06-19 9:37 ` [PATCH v5 01/14] tcg: expose TCGCond manipulation routines Alessandro Di Federico via
2021-06-19 13:51 ` Richard Henderson
2021-06-19 9:37 ` [PATCH v5 02/14] target/hexagon: update MAINTAINERS for idef-parser Alessandro Di Federico via
2021-06-19 9:37 ` [PATCH v5 03/14] target/hexagon: import README " Alessandro Di Federico via
2021-06-23 15:46 ` Taylor Simpson
2021-06-24 13:51 ` Alessandro Di Federico via
2021-06-19 9:37 ` [PATCH v5 04/14] target/hexagon: make slot number an unsigned Alessandro Di Federico via
2021-06-23 15:58 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 05/14] target/hexagon: make helper functions non-static Alessandro Di Federico via
2021-06-23 18:29 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 06/14] target/hexagon: introduce new helper functions Alessandro Di Federico via
2021-06-23 12:05 ` Taylor Simpson
2021-06-23 18:49 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 07/14] target/hexagon: expose next PC in DisasContext Alessandro Di Federico via
2021-06-23 18:54 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 08/14] target/hexagon: prepare input for the idef-parser Alessandro Di Federico via
2021-06-23 19:37 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 09/14] target/hexagon: import lexer for idef-parser Alessandro Di Federico via
2021-06-23 20:05 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 10/14] target/hexagon: import parser " Alessandro Di Federico via
2021-06-22 22:35 ` Taylor Simpson
2021-06-24 3:55 ` Taylor Simpson
2021-06-29 14:26 ` Alessandro Di Federico via
2021-06-30 16:51 ` Paolo Montesel
2021-07-05 16:47 ` Alessandro Di Federico via
2021-06-19 9:37 ` [PATCH v5 11/14] target/hexagon: call idef-parser functions Alessandro Di Federico via
2021-06-25 22:00 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 12/14] target/hexagon: remove unused macros and functions Alessandro Di Federico via
2021-06-25 22:02 ` Taylor Simpson
2021-06-19 9:37 ` [PATCH v5 13/14] target/hexagon: import additional tests Alessandro Di Federico via
2021-06-25 23:56 ` Taylor Simpson
2021-06-28 22:39 ` Taylor Simpson
2021-07-05 16:50 ` Alessandro Di Federico via
2021-06-19 9:37 ` [PATCH v5 14/14] gitlab-ci: do not use qemu-project Docker registry Alessandro Di Federico via
2021-06-29 14:26 ` Alessandro Di Federico via
2021-06-29 14:37 ` Daniel P. Berrangé [this message]
2021-07-08 16:00 ` Alessandro Di Federico via
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=YNswId7vQL/zYJCR@redhat.com \
--to=berrange@redhat.com \
--cc=ale.qemu@rev.ng \
--cc=ale@rev.ng \
--cc=babush@rev.ng \
--cc=bcain@quicinc.com \
--cc=nizzo@rev.ng \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=tsimpson@quicinc.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).