From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: Willian Rampazzo <willianr@redhat.com>,
Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
f4bug@amsat.org,
Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [RFC PATCH] gitlab: add special rule for the hexagon container
Date: Mon, 24 May 2021 07:35:59 -0700 [thread overview]
Message-ID: <eb50c468-83d2-516f-adaa-ec7941ab0f8a@linaro.org> (raw)
In-Reply-To: <20210520151924.5063-1-alex.bennee@linaro.org>
On 5/20/21 8:19 AM, Alex Bennée wrote:
> The hexagon container is always manually built but of course not
> everyone will be building it themselves and pushing to their
> registries. We still need to create a "local" registry copy for the
> actual gitlab tests to run. We don't build it in this case, just pull
> it across from the upstream registry. We disable this rule from
> running on the qemu-project itself so it doesn't accidentally wipe out
> our master copy.
>
> Fixes: 910c40ee94 ("gitlab: add build-user-hexagon test")
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: Cornelia Huck <cohuck@redhat.com>
> ---
I get
Found errors in your .gitlab-ci.yml:
jobs:build-user-hexagon:needs config uses invalid types: bridge
r~
> .gitlab-ci.d/containers.yml | 27 +++++++++++++++++++++++++++
> .gitlab-ci.yml | 2 ++
> 2 files changed, 29 insertions(+)
>
> diff --git a/.gitlab-ci.d/containers.yml b/.gitlab-ci.d/containers.yml
> index 3fb3c14f06..088c7e68c3 100644
> --- a/.gitlab-ci.d/containers.yml
> +++ b/.gitlab-ci.d/containers.yml
> @@ -101,6 +101,33 @@ armhf-debian-cross-container:
> variables:
> NAME: debian-armhf-cross
>
> +# We never want to build hexagon in the CI system and by default we
> +# always want to refer to the master registry where it lives.
> +hexagon-cross-container:
> + image: docker:stable
> + stage: containers
> + except:
> + variables:
> + - $CI_PROJECT_NAMESPACE == 'qemu-project'
> + variables:
> + NAME: debian-hexagon-cross
> + GIT_DEPTH: 1
> + services:
> + - docker:dind
> + before_script:
> + - export TAG="$CI_REGISTRY_IMAGE/qemu/$NAME:latest"
> + - export COMMON_TAG="$CI_REGISTRY/qemu-project/qemu/qemu/$NAME:latest"
> + - docker info
> + - docker login $CI_REGISTRY -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD"
> + script:
> + - echo "TAG:$TAG"
> + - echo "COMMON_TAG:$COMMON_TAG"
> + - docker pull $COMMON_TAG
> + - docker tag $COMMON_TAG $TAG
> + - docker push "$TAG"
> + after_script:
> + - docker logout
> +
> hppa-debian-cross-container:
> extends: .container_job_template
> stage: containers-layer2
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index f718b61fa7..a04cca9db0 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -421,6 +421,8 @@ build-user-static:
> # declared. The image is manually uploaded.
> build-user-hexagon:
> extends: .native_build_job_template
> + needs:
> + hob: hexagon-cross-container
> variables:
> IMAGE: debian-hexagon-cross
> TARGETS: hexagon-linux-user
>
next prev parent reply other threads:[~2021-05-24 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 15:19 [RFC PATCH] gitlab: add special rule for the hexagon container Alex Bennée
2021-05-24 14:35 ` Richard Henderson [this message]
2021-05-24 14:49 ` Daniel P. Berrangé
2021-05-24 15:04 ` 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=eb50c468-83d2-516f-adaa-ec7941ab0f8a@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.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).