gitlab-ci: More stable URL for kernel and ramdisk artifacts, for LAVA
authorTomeu Vizoso <tomeu.vizoso@collabora.com>
Wed, 1 Apr 2020 11:07:46 +0000 (13:07 +0200)
committerMarge Bot <eric+marge@anholt.net>
Tue, 7 Jul 2020 11:52:30 +0000 (11:52 +0000)
commitdcd171f5e9bd612b33144c90e4b0c1ac919498f0
tree266e0bbc66ef997799249f4663be29f5c84a6853
parentbf3d4b1adde4c354ac31e2d7a679dc3946f4abc2
gitlab-ci: More stable URL for kernel and ramdisk artifacts, for LAVA

Place the kernel and ramdisk into a place in the file server so the URL
will only change when the contents also change.

Also put the Mesa build into a separate tarball so the ramdisk's
contents don't change every build.

With proper caching in place, all devices in the same farm need only to
download the mesa tarball once, saving time.

As we switch to MinIO for making kernels and rootfs available to LAVA
devices, we can stop using Docker to distribute them.

Instead, build when needed in separate jobs that push directly to MinIO,
from where LAVA devices can download them.

Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Acked-by: Daniel Stone <daniels@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5515>
.gitlab-ci.yml
.gitlab-ci/container/arm_build.sh
.gitlab-ci/container/cross_build.sh
.gitlab-ci/container/lava_arm.sh [changed mode: 0644->0755]
.gitlab-ci/create-rootfs.sh
.gitlab-ci/generate_lava.py
.gitlab-ci/lava-deqp.yml.jinja2
.gitlab-ci/lava-gitlab-ci.yml
.gitlab-ci/prepare-artifacts.sh