From: Heinrich Schuchardt <hidden> Date: 2019-08-04 13:04:40
For GitLab we create our own GRUB binaries. Use them for Travis CI too.
Signed-off-by: Heinrich Schuchardt <redacted>
---
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
Best regards
Heinrich
---
.travis.yml | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
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 <redacted>
---
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
From: Heinrich Schuchardt <hidden> Date: 2019-08-05 20:11:58
On 8/5/19 3:17 PM, Tom Rini wrote:
On Sun, Aug 04, 2019 at 03:04:40PM +0200, Heinrich Schuchardt wrote:
quoted
For GitLab we create our own GRUB binaries. Use them for Travis CI too.
Signed-off-by: Heinrich Schuchardt <redacted>
---
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.
We would still be downloading gitabyes where we only need a few MBs of
files.
Best regards
Heinrich
On Mon, Aug 05, 2019 at 10:11:58PM +0200, Heinrich Schuchardt wrote:
On 8/5/19 3:17 PM, Tom Rini wrote:
quoted
On Sun, Aug 04, 2019 at 03:04:40PM +0200, Heinrich Schuchardt wrote:
quoted
For GitLab we create our own GRUB binaries. Use them for Travis CI too.
Signed-off-by: Heinrich Schuchardt <redacted>
---
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.
We would still be downloading gitabyes where we only need a few MBs of
files.
Yes, but we could also kill out some building time with the move to
xenial, might end up being no real change in overall time.
--
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/181dc1b5/attachment.sig>