From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC DO-NOT-APPLY 1/1] .travis.yml: use GRUB from Docker image
Date: Mon, 5 Aug 2019 09:17:47 -0400 [thread overview]
Message-ID: <20190805131747.GD9594@bill-the-cat> (raw)
In-Reply-To: <20190804130440.14375-1-xypron.glpk@gmx.de>
On Sun, Aug 04, 2019 at 03:04:40PM +0200, Heinrich Schuchardt wrote:
> For GitLab we create our own GRUB binaries. Use them for Travis CI too.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> Hello Tom,
>
> with this patch every single of the 78 sub-job will pull our Docker image
> resulting in 78 times 2GB traffic and 78 times 3 min for pulling the image.
>
> This cannot be the right way to do it. I think it would be preferable to
> copy our GRUB images only. Can't we have a repository on gitlab.denx.de
> where we put all Travis CI binary dependencies:
>
> * GRUB images
> * QEMU images
> * cross compilers
I was hoping that we could tell Travis to just fully use our Docker
images. Looking at
https://docs.travis-ci.com/user/build-stages/share-docker-image/ maybe
we can just restrict the Docker pull to the test.py stages that use GRUB
for tests? And then as part of a move to Xenial we could also copy out
QEMU.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190805/f1f217e7/attachment.sig>
next prev parent reply other threads:[~2019-08-05 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 13:04 [U-Boot] [RFC DO-NOT-APPLY 1/1] .travis.yml: use GRUB from Docker image Heinrich Schuchardt
2019-08-05 13:17 ` Tom Rini [this message]
2019-08-05 20:11 ` Heinrich Schuchardt
2019-08-05 20:14 ` Tom Rini
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=20190805131747.GD9594@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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