From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>, Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org,
Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [PATCH RFC 2/3] gitlab: build all container images during CI
Date: Mon, 22 Jun 2020 18:13:59 +0200 [thread overview]
Message-ID: <461c7576-89cd-be6a-d6d0-026645231cb4@redhat.com> (raw)
In-Reply-To: <20200622154611.GJ736373@redhat.com>
On 6/22/20 5:46 PM, Daniel P. Berrangé wrote:
> On Mon, Jun 22, 2020 at 05:38:16PM +0200, Philippe Mathieu-Daudé wrote:
>> On 6/22/20 5:33 PM, Daniel P. Berrangé wrote:
>>> We have a number of container images in tests/docker/dockerfiles
>>> that are intended to provide well defined environments for doing
>>> test builds. We want our CI system to use these containers too.
>>>
>>> This introduces builds of all of them as the first stage in the
>>> CI, so that the built containers are available for later build
>>> jobs. The containers are setup to use the GitLab container
>>> registry as the cache, so we only pay the penalty of the full
>>> build when the dockerfiles change. The main qemu-project/qemu
>>> repo is used as a second cache, so that users forking QEMU will
>>> see a fast turnaround time on their CI jobs.
>>
>> OMG you did it! Lovely... 😍
>>
>> Looking at https://gitlab.com/berrange/qemu/-/pipelines/158854797
>> why gitlab isn't caching the docker images? the cache isn't
>> populated on all the runners yet? Or we have to use the same
>> runner again to hit its cache?
>
> It is caching it but it isn't obvious what to look for.
>
> The "docker build" command is always still run, but you'll
> notice each of the actual commands in the dockerfile are
> followed by a message " ---> Using cache", instead of the
> normal command output.
Indeed!
>
> Compare the "amd64-debian9-container" job as an example.
>
> Here is the output seen in the original job which actually did a real
> build:
>
> https://gitlab.com/berrange/qemu/-/jobs/605783351
>
> And here is the output from the pipeline you point to above:
>
> https://gitlab.com/berrange/qemu/-/jobs/606175855
>
> The cached case is still taking 2 mins 30 seconds, but the original
> full build took 4 mins 50 seconds.
>
> The difference will be more noticable if we expand the list of packages
> install in the images to cover more of QEMU's possible dependancies.
The difference is already very noticeable on my host:
$ time docker pull registry.gitlab.com/berrange/qemu/ci-centos8:latest
latest: Pulling from berrange/qemu/ci-centos8
8a29a15cefae: Pull complete
4a748adf2909: Pull complete
3c034506a458: Pull complete
cd48de325fa1: Pull complete
Digest:
sha256:a6580433f5456d7c49e2b9b796c717c79a5fa15f4eecf71bdbcffd9df6b8217a
Status: Downloaded newer image for
registry.gitlab.com/berrange/qemu/ci-centos8:latest
registry.gitlab.com/berrange/qemu/ci-centos8:latest
real 0m53.566s
user 0m0.115s
sys 0m0.081s
>
> Regards,
> Daniel
>
next prev parent reply other threads:[~2020-06-22 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 15:33 [PATCH RFC 0/3] gitlab: build containers to use in build jobs Daniel P. Berrangé
2020-06-22 15:33 ` [PATCH RFC 1/3] gitlab: introduce explicit "container" and "build" stages Daniel P. Berrangé
2020-06-22 15:59 ` Laszlo Ersek
2020-06-25 8:54 ` Thomas Huth
2020-06-25 8:58 ` Philippe Mathieu-Daudé
2020-06-22 15:33 ` [PATCH RFC 2/3] gitlab: build all container images during CI Daniel P. Berrangé
2020-06-22 15:38 ` Philippe Mathieu-Daudé
2020-06-22 15:46 ` Daniel P. Berrangé
2020-06-22 16:13 ` Philippe Mathieu-Daudé [this message]
2020-06-22 18:26 ` Alex Bennée
2020-06-23 8:47 ` Daniel P. Berrangé
2020-06-23 9:35 ` Alex Bennée
2020-06-25 9:35 ` Thomas Huth
2020-06-25 9:50 ` Daniel P. Berrangé
2020-06-25 15:57 ` Laszlo Ersek
2020-06-25 10:07 ` Daniel P. Berrangé
2020-06-25 11:14 ` Alex Bennée
2020-06-25 10:14 ` Thomas Huth
2020-06-25 10:24 ` Daniel P. Berrangé
2020-06-25 13:25 ` Thomas Huth
2020-06-25 14:29 ` Daniel P. Berrangé
2020-06-22 15:33 ` [PATCH RFC 3/3] gitlab: convert jobs to use custom built containers Daniel P. Berrangé
2020-06-25 9:59 ` Thomas Huth
2020-06-25 10:31 ` [PATCH RFC 0/3] gitlab: build containers to use in build jobs Alex Bennée
2020-06-25 11:15 ` Thomas Huth
2020-06-25 11:26 ` Daniel P. Berrangé
2020-06-25 11:29 ` Daniel P. Berrangé
2020-06-25 11:33 ` Thomas Huth
2020-06-25 11:39 ` Daniel P. Berrangé
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=461c7576-89cd-be6a-d6d0-026645231cb4@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).