Skip to contentSkip to conversation

.travis.yml: use GRUB from Docker image

RFC New Heinrich Schuchardt 2 participants 4 messages Aug 4, 2019 – Aug 5, 2019

lore
Share & tools
lore
#0 lore raw

RFC 1/1 .travis.yml: use GRUB from Docker image

For GitLab we create our own GRUB binaries. Use them for Travis CI too.

---
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(-)
.travis.yml +14 -4
index 38fc10318e..6c1dc53fe4 100644
@@ -8,6 +8,9 @@ dist: trusty
 
 language: c
 
+services:
+ - docker
+
 addons:
   apt:
     sources:
@@ -54,10 +57,17 @@ install:
  - pip install pyelftools
  - grub-mkimage -o ~/grub_x86.efi -O i386-efi normal  echo lsefimmap lsefi lsefisystab efinet tftp minicmd
  - grub-mkimage -o ~/grub_x64.efi -O x86_64-efi normal  echo lsefimmap lsefi lsefisystab efinet tftp minicmd
- - mkdir ~/grub2-arm
- - ( cd ~/grub2-arm; wget -O - http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/repo/oss/suse/armv7hl/grub2-arm-efi-2.02~beta2-87.1.armv7hl.rpm | rpm2cpio | cpio -di )
- - mkdir ~/grub2-arm64
- - ( cd ~/grub2-arm64; wget -O - http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/repo/oss/suse/aarch64/grub2-arm64-efi-2.02~beta2-87.1.aarch64.rpm | rpm2cpio | cpio -di )
+ - export DOCKER_IMAGE=trini/u-boot-gitlab-ci-runner:xenial-20190720-29Jul2019
+ - sudo docker pull $DOCKER_IMAGE
+ - sudo docker create -ti $DOCKER_IMAGE
+ - export DOCKER_CONTAINER=$(sudo docker ps -aqf "ancestor=$DOCKER_IMAGE")
+ - mkdir -p ~/grub2-arm/usr/lib/efi/
+ - mkdir -p ~/grub2-arm/usr/lib/grub2/arm-efi/
+ - sudo docker cp $DOCKER_CONTAINER:/opt/grub/grubarm.efi ~/grub2-arm/usr/lib/efi/
+ - sudo docker cp $DOCKER_CONTAINER:/opt/grub/grubaa64.efi ~/grub2-arm/usr/lib/grub2/arm-efi/
+ - sudo docker rm $DOCKER_CONTAINER
+ - unset DOCKER_CONTAINER
+ - unset DOCKER_IMAGE
 
 env:
   global:

--
2.20.1

#1 lore raw

RFC 1/1 .travis.yml: use GRUB from Docker image

Quoted 9 lines · Heinrich Schuchardt

For GitLab we create our own GRUB binaries. Use them for Travis CI too.

---
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.

Quoted 7 lines

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.

Signature · 8 lines
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>
#2 lore raw

RFC 1/1 .travis.yml: use GRUB from Docker image

Quoted 18 lines · Tom Rini
Quoted 9 lines · Heinrich Schuchardt

For GitLab we create our own GRUB binaries. Use them for Travis CI too.

---
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.

Quoted 7 lines

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

Quoted 7 lines

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

#3 lore raw

RFC 1/1 .travis.yml: use GRUB from Docker image

Quoted 26 lines · Heinrich Schuchardt
Quoted 18 lines · Tom Rini
Quoted 9 lines · Heinrich Schuchardt

For GitLab we create our own GRUB binaries. Use them for Travis CI too.

---
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.

Quoted 7 lines

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

Quoted 6 lines

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.

Quoted 2 lines

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.

Signature · 8 lines
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>