qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: fam@euphon.net, berrange@redhat.com, qemu-devel@nongnu.org,
	f4bug@amsat.org, stefanha@redhat.com, crosa@redhat.com,
	pbonzini@redhat.com, aurelien@aurel32.net
Subject: Re: [PATCH v2 5/6] docs/devel: update the container based tests
Date: Mon, 22 Feb 2021 12:14:33 +0000	[thread overview]
Message-ID: <874ki470zp.fsf@linaro.org> (raw)
In-Reply-To: <a28b2c23-418b-83f7-c045-e82a11b95ae3@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> On 22/02/2021 11.14, Alex Bennée wrote:
>> This section has grown a little stale so clean-up the language and
>> examples for current usage:
>> 
>>    - refer to containers at the top
>>    - mention podman can also be used
>>    - add podman prerequisites section
>>    - move to using "docker-help" for online help
>>    - mention the registry and it's purpose
>>    - don't refer to out-of-date min-glib image
>> 
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Cc: Thomas Huth <thuth@redhat.com>
>> ---
>>   docs/devel/testing.rst | 61 +++++++++++++++++++++++++++++++-----------
>>   1 file changed, 46 insertions(+), 15 deletions(-)
> [...]
>>   .. code::
>>   
>> -  make docker-test-build@min-glib
>> +  make docker-test-build@centos7
>>   
>> -This will create a container instance using the ``min-glib`` image (the image
>> +This will create a container instance using the ``centos7`` image (the image
>>   is downloaded and initialized automatically), in which the ``test-build`` job
>>   is executed.
>
> We're going to drop support for CentOS 7 in three months (May) ... so maybe 
> it makes more sense to directly use centos8 or another long-term distro here?
>
>> +Registry
>> +--------
>> +
>> +The QEMU project has a container registry hosted by GitLab at
>> +``registry.gitlab.com/qemu-project/qemu`` which will automatically be
>> +used to pull in pre-built layers. This avoids unnecessary strain on
>> +the distro archives created by multiple developers running the same
>> +container build steps over and over again. This can be overridden
>> +locally by using the ``NOCACHE`` build option:
>
> Thanks a lot for adding the information!
>
>   Thomas

Is that a r-b if I change to centos8?

-- 
Alex Bennée


  reply	other threads:[~2021-02-22 12:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 10:14 [PATCH v2 0/6] testing/next (meson check-tcg, fedora bump, docs) Alex Bennée
2021-02-22 10:14 ` [PATCH v2 1/6] meson.build: expose TCG cross compiler information in summary Alex Bennée
2021-02-22 10:14 ` [PATCH v2 2/6] docker: Bump Fedora images to release 33 Alex Bennée
2021-02-22 10:14 ` [PATCH v2 3/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test Alex Bennée
2021-02-22 15:44   ` Probing Meson for build configurations (was: [PATCH v2 3/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test) Wainer dos Santos Moschetta
2021-02-22 16:05     ` Daniel P. Berrangé
2021-02-22 10:14 ` [PATCH v2 4/6] docs/devel: expand on use of containers to build tests Alex Bennée
2021-02-22 11:39   ` Thomas Huth
2021-02-22 10:14 ` [PATCH v2 5/6] docs/devel: update the container based tests Alex Bennée
2021-02-22 11:46   ` Thomas Huth
2021-02-22 12:14     ` Alex Bennée [this message]
2021-02-22 12:15       ` Thomas Huth
2021-02-22 10:14 ` [PATCH v2 6/6] docs/devel: add forward reference to check-tcg Alex Bennée
2021-02-22 11:36   ` Philippe Mathieu-Daudé
2021-02-22 12:16   ` Thomas Huth
2021-02-24  3:33 ` [PATCH v2 0/6] testing/next (meson check-tcg, fedora bump, docs) Richard Henderson

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=874ki470zp.fsf@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 \
    /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).