# no need to pull the whole repo to build the container image
GIT_STRATEGY: none
-# Debian 10 based x86 build image
-x86_build:
+# Debian 10 based x86 build image base
+x86_build-base:
extends:
- .fdo.container-build@debian
- .container
variables:
- FDO_DISTRIBUTION_TAG: &x86_build "2020-05-31"
+ FDO_DISTRIBUTION_TAG: &x86_build-base "2020-06-02"
+
+.use-x86_build-base:
+ extends:
+ - x86_build-base
+ - .ci-run-policy
+ stage: container-2
+ variables:
+ BASE_TAG: *x86_build-base
+ FDO_BASE_IMAGE: "$CI_REGISTRY_IMAGE/debian/x86_build-base:$BASE_TAG"
+ needs:
+ - x86_build-base
+
+# Debian 10 based x86 main build image
+x86_build:
+ extends:
+ - .use-x86_build-base
+ variables:
+ FDO_DISTRIBUTION_TAG: &x86_build "2020-06-02"
.use-x86_build:
variables:
TAG: *x86_build
image: "$CI_REGISTRY_IMAGE/debian/x86_build:$TAG"
needs:
+ - x86_build-base
- x86_build
+# Debian 10 based i386 cross-build image
+i386_build:
+ extends:
+ - .use-x86_build-base
+ variables:
+ FDO_DISTRIBUTION_TAG: &i386_build "2020-06-02"
+
+.use-i386_build:
+ variables:
+ TAG: *i386_build
+ image: "$CI_REGISTRY_IMAGE/debian/i386_build:$TAG"
+ needs:
+ - x86_build-base
+ - i386_build
+
+# Debian 10 based ppc64el cross-build image
+ppc64el_build:
+ extends:
+ - .use-x86_build-base
+ variables:
+ FDO_DISTRIBUTION_TAG: &ppc64el_build "2020-06-02"
+
+.use-ppc64el_build:
+ variables:
+ TAG: *ppc64el_build
+ image: "$CI_REGISTRY_IMAGE/debian/ppc64el_build:$TAG"
+ needs:
+ - x86_build-base
+ - ppc64el_build
+
+# Debian 10 based s390x cross-build image
+s390x_build:
+ extends:
+ - .use-x86_build-base
+ variables:
+ FDO_DISTRIBUTION_TAG: &s390x_build "2020-06-02"
+
+.use-s390x_build:
+ variables:
+ TAG: *s390x_build
+ image: "$CI_REGISTRY_IMAGE/debian/s390x_build:$TAG"
+ needs:
+ - x86_build-base
+ - s390x_build
+
# Debian 10 based x86 test image base
x86_test-base:
- extends: x86_build
+ extends: x86_build-base
variables:
- FDO_DISTRIBUTION_TAG: &x86_test-base "2020-06-01"
+ FDO_DISTRIBUTION_TAG: &x86_test-base "2020-06-02"
.use-x86_test-base:
extends:
- - x86_build
+ - x86_build-base
- .ci-run-policy
stage: container-2
variables:
x86_test-gl:
extends: .use-x86_test-base
variables:
- FDO_DISTRIBUTION_TAG: &x86_test-gl "2020-06-01"
+ FDO_DISTRIBUTION_TAG: &x86_test-gl "2020-06-03"
# Debian 10 based x86 test image for VK
x86_test-vk:
extends: .use-x86_test-base
variables:
- FDO_DISTRIBUTION_TAG: &x86_test-vk "2020-06-01"
+ FDO_DISTRIBUTION_TAG: &x86_test-vk "2020-06-02"
# Debian 9 based x86 build image (old LLVM)
x86_build_old:
- extends: x86_build
+ extends: x86_build-base
variables:
FDO_DISTRIBUTION_TAG: &x86_build_old "2020-06-02"
FDO_DISTRIBUTION_VERSION: stretch-slim
# x86 image with ARM rootfses for baremetal testing.
arm_test:
- extends: x86_build
+ extends: x86_build-base
variables:
FDO_DISTRIBUTION_TAG: &arm_test "2020-06-01"
-D werror=true
meson-i386:
- extends: .meson-cross
+ extends:
+ - .meson-cross
+ - .use-i386_build
variables:
CROSS: i386
VULKAN_DRIVERS: intel,amd
EXTRA_OPTION: >
-D vulkan-overlay-layer=true
-D werror=true
- script:
- - dpkg -i /var/cache/apt/archives/$CROSS/*.deb
- - .gitlab-ci/meson-build.sh
meson-s390x:
extends:
- .meson-cross
+ - .use-s390x_build
tags:
- kvm
variables:
EXTRA_OPTION: >
-D werror=true
GALLIUM_DRIVERS: "swrast"
- script:
- # For unknown reasons "too many" installed i386 libraries cause qemu to
- # crash while executing llvm-config for s390x.
- - apt-get purge -y wine32-development
- - apt-get autoremove -y --purge
- - dpkg -i /var/cache/apt/archives/$CROSS/*.deb
- - .gitlab-ci/meson-build.sh
meson-ppc64el:
extends:
- meson-s390x
+ - .use-ppc64el_build
variables:
CROSS: ppc64el
EXTRA_OPTION: ""
TAG: *x86_test-gl
image: "$CI_REGISTRY_IMAGE/debian/x86_test-gl:$TAG"
needs:
+ - x86_build-base
- x86_build
- meson-testing
- x86_test-base
TAG: *x86_test-vk
image: "$CI_REGISTRY_IMAGE/debian/x86_test-vk:$TAG"
needs:
+ - x86_build-base
- x86_build
- meson-testing
- x86_test-base
DEQP_VER: gles31
IR3_SHADER_DEBUG: nouboopt
DEQP_CASELIST_FILTER: "functional.*ubo"
- DEQP_EXPECTED_FAILS: deqp-freedreno-a630-noubo-fails.txt
# The driver does some guessing as to whether to render using gmem
# or bypass, and some GLES3.1 features interact with either one.