mirrors
/
weston
mirror of https://gitlab.freedesktop.org/wayland/weston.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
weston/.gitlab-ci.yml

616 lines
16 KiB
YAML
Raw Normal View History

CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
# vim: set expandtab shiftwidth=2 tabstop=8 textwidth=0:
CI: Upgrade ci-templates version This is required to support Debian bookworm. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-06-12 11:50:03 +03:00
.templates_sha: &template_sha 184ca628f89f3193c249b4e34e45afee2773a833 # see https://docs.gitlab.com/ee/ci/yaml/#includefile
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# This file uses the freedesktop ci-templates to build Weston and run our
# tests in CI.
ci: upgrade seatd to 0.6 This upgrades seatd to the latest version. Examples are disabled by default. Man pages are already disabled by auto_features=disabled. Other build options have been renamed. Signed-off-by: Simon Ser <contact@emersion.fr>
2021-09-12 14:48:41 +03:00
#
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# ci-templates uses a multi-stage build process. First, the base container
# image is built which contains the core distribution, the toolchain, and
# all our build dependencies. This container is aggressively cached; if a
# container image matching $FDO_DISTRIBUTION_TAG is found in either the
# upstream repo (wayland/weston) or the user's downstream repo, it is
# reused for the build. This gives us predictability of build and far
# quicker runtimes, however it means that any changes to the base container
# must also change $FDO_DISTRIBUTION_TAG. When changing this, please use
# the current date as well as a unique build identifier.
#
# After the container is either rebuilt (tag mismatch) or reused (tag
# previously used), the build stage executes within this container.
#
# The final stage is used to expose documentation and coverage information,
# including publishing documentation to the public site when built on the
# main branch.
#
# Apart from the 'variables', 'include', and 'stages' top-level anchors,
# everything not beginning with a dot ('.') is the name of a job which will
# be executed as part of CI, unless the rules specify that it should not be
# run.
#
# Variables prefixed with CI_ are generally provided by GitLab itself;
# variables prefixed with FDO_ and templates prefixed by .fdo are provided
# by the ci-templates.
#
# For more information on GitLab CI, including the YAML syntax, see:
# https://docs.gitlab.com/ee/ci/yaml/README.html
#
# Note that freedesktop.org uses the 'Community Edition' of GitLab, so features
# marked as 'premium' or 'ultimate' are not available to us.
#
# For more information on ci-templates, see:
# - documentation at https://freedesktop.pages.freedesktop.org/ci-templates/
# - repo at https://gitlab.freedesktop.org/freedesktop/ci-templates/
ci: Update ci-templates to newer version [daniels: Extracted from previous patch, updated to even-newer version.] Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2021-07-31 17:07:58 +03:00
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
variables:
gitlab CI: update to recent fdo ci-templates Make use of the templating structure the templates provide. No functional changes in the end, container-build's default behavior is the previously called container-if-not-exists template. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:33:57 +03:00
FDO_UPSTREAM_REPO: wayland/weston
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
FDO_REPO_SUFFIX: "$BUILD_OS-$FDO_DISTRIBUTION_VERSION/$BUILD_ARCH"
Add support for FreeRDP 3.x With this, Weston can build against either FreeRDP 3.x or 2.x depending on what has been detected by meson (3.x takes priority). The main source of changes is the settings are now opaque and require the use of accessors. That was pretty mechanical and seems to work on 2.x as well. There are a few changes around constants getting a WINPR_ prefix, the UTF conversion functions we used are obsolete, so use the proper "new" ones, and other fairly minor things. The key & cert management changed rather completely, libfreerdp won't load files for us, we have to use the helpers to do so, and I *think* the RDP RSA key and SSL key use the same setting location. Seems to work with SSL at least. There was also a minor glitch with keyboard input, KBD_FLAGS_DOWN is basically never set. It appears to be an upstream FreeRDP change in 3.x, it was being set incorrectly (always on any key down) while it should only be set on repeats. However the fastpath input code has no way to set it from what I can tell, so it's just loss. We instead ignore it. Note that the screen size is odd (and different between freerdp client and remmina), it also won't adjust dynamically when the window is resized. I don't think this relates to my port though, I observe the same behaviour with the packaged FreeRDP 2 based Weston, but I can try to look into it later Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2024-08-02 08:45:33 +03:00
FDO_DISTRIBUTION_TAG: '2024-08-14-00-freerdp3.x'
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
include:
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Here we use a fixed ref in order to isolate ourselves from ci-templates
# API changes. If you need new features from ci-templates you must bump
# this to the current SHA you require from the ci-templates repo, however
# be aware that you may need to account for API changes when doing so.
gitlab ci: switch to freedesktop ci-templates The project was moved a while ago to make it look less waylandy. Same sha, so no actual changes here. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:25:48 +03:00
- project: 'freedesktop/ci-templates'
ci: Update ci-templates to newer version [daniels: Extracted from previous patch, updated to even-newer version.] Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2021-07-31 17:07:58 +03:00
ref: *template_sha
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
file: '/templates/debian.yml'
ci: Use ci-fairy to check for Signed-off-by [daniels: Only run on MRs.] Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2021-07-31 17:12:08 +03:00
- project: 'freedesktop/ci-templates'
ref: *template_sha
file: '/templates/ci-fairy.yml'
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
.default-rules:
rules:
# do not duplicate pipelines on merge pipelines
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS && $CI_PIPELINE_SOURCE == "push"
when: never
# we need a default case though, so all the rest still run
- when: on_success
.merge-rules:
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
when: always
- when: never
Add .gitlab-ci.yml Add a GitLab CI configuration which tests building, 'make check', and 'make distcheck' of the tree inside a Debian Stretch container. The choice of distribution base was arbitrary and may easily be changed. As the version of wayland-protocols available is not sufficiently new, we clone and build our own local version first. libwayland is new enough, however we could potentially reuse the artifacts generated by the Wayland CI job. When commits are pushed to upstream, the commits will run this CI pipeline to run these tests, and capture the result as an artifact bundle, including the compiled binaries and full test suite logs. Results can be seen at: https://gitlab.freedesktop.org/wayland/weston/pipelines/ Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-06-06 00:20:40 +03:00
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Define the build stages. These are used for UI grouping as well as
# dependencies.
Add .gitlab-ci.yml Add a GitLab CI configuration which tests building, 'make check', and 'make distcheck' of the tree inside a Debian Stretch container. The choice of distribution base was arbitrary and may easily be changed. As the version of wayland-protocols available is not sufficiently new, we clone and build our own local version first. libwayland is new enough, however we could potentially reuse the artifacts generated by the Wayland CI job. When commits are pushed to upstream, the commits will run this CI pipeline to run these tests, and capture the result as an artifact bundle, including the compiled binaries and full test suite logs. Results can be seen at: https://gitlab.freedesktop.org/wayland/weston/pipelines/ Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-06-06 00:20:40 +03:00
stages:
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
- "Merge request checks"
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- "Pre Base container"
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
- "Base container"
- "Full build and test"
- "No-GL build and test"
- "Other builds"
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
- pages
Add .gitlab-ci.yml Add a GitLab CI configuration which tests building, 'make check', and 'make distcheck' of the tree inside a Debian Stretch container. The choice of distribution base was arbitrary and may easily be changed. As the version of wayland-protocols available is not sufficiently new, we clone and build our own local version first. libwayland is new enough, however we could potentially reuse the artifacts generated by the Wayland CI job. When commits are pushed to upstream, the commits will run this CI pipeline to run these tests, and capture the result as an artifact bundle, including the compiled binaries and full test suite logs. Results can be seen at: https://gitlab.freedesktop.org/wayland/weston/pipelines/ Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-06-06 00:20:40 +03:00
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Base variables used for anything using a Debian environment
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.os-debian-lts:
gitlab CI: update to recent fdo ci-templates Make use of the templating structure the templates provide. No functional changes in the end, container-build's default behavior is the previously called container-if-not-exists template. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:33:57 +03:00
variables:
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
BUILD_OS: debian
CI: Parameterise LLVM version Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:22:26 +03:00
LLVM_VERSION: 11
Add support for FreeRDP 3.x With this, Weston can build against either FreeRDP 3.x or 2.x depending on what has been detected by meson (3.x takes priority). The main source of changes is the settings are now opaque and require the use of accessors. That was pretty mechanical and seems to work on 2.x as well. There are a few changes around constants getting a WINPR_ prefix, the UTF conversion functions we used are obsolete, so use the proper "new" ones, and other fairly minor things. The key & cert management changed rather completely, libfreerdp won't load files for us, we have to use the helpers to do so, and I *think* the RDP RSA key and SSL key use the same setting location. Seems to work with SSL at least. There was also a minor glitch with keyboard input, KBD_FLAGS_DOWN is basically never set. It appears to be an upstream FreeRDP change in 3.x, it was being set incorrectly (always on any key down) while it should only be set on repeats. However the fastpath input code has no way to set it from what I can tell, so it's just loss. We instead ignore it. Note that the screen size is odd (and different between freerdp client and remmina), it also won't adjust dynamically when the window is resized. I don't think this relates to my port though, I observe the same behaviour with the packaged FreeRDP 2 based Weston, but I can try to look into it later Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2024-08-02 08:45:33 +03:00
FREERDP_VERSION: 2
ci: Move Debian from Buster to Bullseye Now Debian 11 (Bullseye) has been released, shift our CI builds to using that instead of the older Buster. Due to dependency-chain changes, we have to install a lot more packages explicitly and retain more at runtime. This is exacerbated by pkg-config now requiring the entire chain to be installed, not just the immediate dependencies. Our documentation toolchain also gets bumped to a higher version to deal with Doxygen changes. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-16 18:49:52 +03:00
FDO_DISTRIBUTION_VERSION: bullseye
CI: Force pip to install packages Newer versions of Debian make you pass --break-system-packages to pip in order for it to install packages. Since we do want to keep using pip for controlled versions rather than the distribution packages, add this flag. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:41:54 +03:00
FDO_DISTRIBUTION_EXEC: 'env FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} BUILD_ARCH=${BUILD_ARCH} KERNEL_IMAGE=${KERNEL_IMAGE} KERNEL_DEFCONFIG=${KERNEL_DEFCONFIG} LLVM_VERSION=${LLVM_VERSION} FDO_DISTRIBUTION_VERSION=${FDO_DISTRIBUTION_VERSION} bash .gitlab-ci/debian-install.sh'
gitlab CI: update to recent fdo ci-templates Make use of the templating structure the templates provide. No functional changes in the end, container-build's default behavior is the previously called container-if-not-exists template. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:33:57 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.os-debian:
variables:
BUILD_OS: debian
LLVM_VERSION: 15
Add support for FreeRDP 3.x With this, Weston can build against either FreeRDP 3.x or 2.x depending on what has been detected by meson (3.x takes priority). The main source of changes is the settings are now opaque and require the use of accessors. That was pretty mechanical and seems to work on 2.x as well. There are a few changes around constants getting a WINPR_ prefix, the UTF conversion functions we used are obsolete, so use the proper "new" ones, and other fairly minor things. The key & cert management changed rather completely, libfreerdp won't load files for us, we have to use the helpers to do so, and I *think* the RDP RSA key and SSL key use the same setting location. Seems to work with SSL at least. There was also a minor glitch with keyboard input, KBD_FLAGS_DOWN is basically never set. It appears to be an upstream FreeRDP change in 3.x, it was being set incorrectly (always on any key down) while it should only be set on repeats. However the fastpath input code has no way to set it from what I can tell, so it's just loss. We instead ignore it. Note that the screen size is odd (and different between freerdp client and remmina), it also won't adjust dynamically when the window is resized. I don't think this relates to my port though, I observe the same behaviour with the packaged FreeRDP 2 based Weston, but I can try to look into it later Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2024-08-02 08:45:33 +03:00
FREERDP_VERSION: 3
USE_BOOKWORM_BACKPORTS: y
CI: work around LeakSanitizer crashes with use_tls=0 Without this fix, we have randomly been getting CI failures due to LeakSanitizer itself crashing after all the tests in a program have succeeded. This has been happening randomly for a long time, but https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1486 made it very reliably repeatable in the job x86_64-debian-full-build (and no other job) in the test-subsurface-shot program. --- Fixture 2 (GL) ok: passed 4, skipped 0, failed 0, total 4 Tracer caught signal 11: addr=0x1b8 pc=0x7f6b3ba640f0 sp=0x7f6b2cc77d10 ==489==LeakSanitizer has encountered a fatal error. I was also able to get a core file after twiddling, but there it ended up with lsan aborting itself rather than a segfault. We got some clues that use_tls=0 might work around this, from https://github.com/google/sanitizers/issues/1342 https://github.com/google/sanitizers/issues/1409 and some other projects that have cargo-culted the same workaround. Using that cause more false leaks to appear, so they need to be suppressed. I suppose we are not interested in catching leaks in glib using code, so I opted to suppress g_malloc0 altogether. Pinpointing it better might have required much more slower stack tracing. wl_shm_buffer_begin_access() uses TLS, so no wonder it gets flagged. ld-*.so is simply uninteresting to us, and it got flagged too. Since this might have been fixed already in LeakSanitizer upstream, who knows, leave some notes to revisit this when we upgrade that in CI. This fix seems to make the branch of https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1486 in my quick testing. Suggested-by: Derek Foreman <derek.foreman@collabora.com> Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2024-04-09 15:41:45 +03:00
# If you upgrade from bookworm, see the use_tls=0 notes in tests/meson.build.
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
FDO_DISTRIBUTION_VERSION: bookworm
FDO_DISTRIBUTION_EXEC: 'env FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} BUILD_ARCH=${BUILD_ARCH} KERNEL_IMAGE=${KERNEL_IMAGE} KERNEL_DEFCONFIG=${KERNEL_DEFCONFIG} LLVM_VERSION=${LLVM_VERSION} FDO_DISTRIBUTION_VERSION=${FDO_DISTRIBUTION_VERSION} bash .gitlab-ci/debian-install.sh'
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
# Does not inherit .default-rules as we only want it to run in MR context.
ci: Use ci-fairy to check for Signed-off-by [daniels: Only run on MRs.] Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2021-07-31 17:12:08 +03:00
check-commit:
extends:
- .fdo.ci-fairy
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .merge-rules
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "Merge request checks"
ci: Use ci-fairy to check for Signed-off-by [daniels: Only run on MRs.] Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2021-07-31 17:12:08 +03:00
script:
- ci-fairy check-commits --signed-off-by --junit-xml=results.xml
gitlab-ci: Use the same name as for check-commits Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2021-10-18 15:50:42 +03:00
- ci-fairy check-merge-request --require-allow-collaboration --junit-xml=results.xml
ci: Use ci-fairy to check for Signed-off-by [daniels: Only run on MRs.] Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2021-07-31 17:12:08 +03:00
variables:
GIT_DEPTH: 100
artifacts:
reports:
junit: results.xml
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.debian-lts-x86_64:
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .os-debian-lts
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
variables:
BUILD_ARCH: "x86-64"
CI: Parameterise kernel build a bit more AArch64 needs different names and paths to x86-64, so let's allow for that. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:16:05 +03:00
KERNEL_IMAGE: "bzImage"
KERNEL_DEFCONFIG: "x86_64_defconfig"
gitlab CI: update to recent fdo ci-templates Make use of the templating structure the templates provide. No functional changes in the end, container-build's default behavior is the previously called container-if-not-exists template. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:33:57 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.debian-x86_64:
extends:
- .os-debian
variables:
BUILD_ARCH: "x86-64"
KERNEL_IMAGE: "bzImage"
KERNEL_DEFCONFIG: "x86_64_defconfig"
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.debian-lts-armv7:
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .os-debian-lts
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
variables:
BUILD_ARCH: "armv7"
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.debian-armv7:
extends:
- .os-debian
variables:
BUILD_ARCH: "armv7"
Add support for FreeRDP 3.x With this, Weston can build against either FreeRDP 3.x or 2.x depending on what has been detected by meson (3.x takes priority). The main source of changes is the settings are now opaque and require the use of accessors. That was pretty mechanical and seems to work on 2.x as well. There are a few changes around constants getting a WINPR_ prefix, the UTF conversion functions we used are obsolete, so use the proper "new" ones, and other fairly minor things. The key & cert management changed rather completely, libfreerdp won't load files for us, we have to use the helpers to do so, and I *think* the RDP RSA key and SSL key use the same setting location. Seems to work with SSL at least. There was also a minor glitch with keyboard input, KBD_FLAGS_DOWN is basically never set. It appears to be an upstream FreeRDP change in 3.x, it was being set incorrectly (always on any key down) while it should only be set on repeats. However the fastpath input code has no way to set it from what I can tell, so it's just loss. We instead ignore it. Note that the screen size is odd (and different between freerdp client and remmina), it also won't adjust dynamically when the window is resized. I don't think this relates to my port though, I observe the same behaviour with the packaged FreeRDP 2 based Weston, but I can try to look into it later Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2024-08-02 08:45:33 +03:00
# Armv7 doesn't have freerdp3 in bookworm-backports so we don't build FreeRDP
MESON_DIST_OPTIONS: "-Dbackend-rdp=false"
# Inhibit installation of freerdp-dev
FREERDP_VERSION: 0
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.debian-lts-aarch64:
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .os-debian-lts
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
variables:
BUILD_ARCH: "aarch64"
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
KERNEL_IMAGE: "Image"
KERNEL_DEFCONFIG: "defconfig"
QEMU_SMP: 8 # built-in QEmu limit
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.debian-aarch64:
extends:
- .os-debian
variables:
BUILD_ARCH: "aarch64"
KERNEL_IMAGE: "Image"
KERNEL_DEFCONFIG: "defconfig"
QEMU_SMP: 8 # built-in QEmu limit
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
base-container-pre:
rules:
gitlab-ci.yml: Always run container jobs to allow page deploy to work Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-11 17:23:33 +03:00
# this run always in merge request
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
when: always
gitlab-ci.yml: Always run container jobs to allow page deploy to work Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-11 17:23:33 +03:00
# run always on main to allow docs to publish
- if: '$CI_PIPELINE_SOURCE == "push" && $CI_PROJECT_PATH == "wayland/weston" && $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH'
when: always
# allow to run manually in a branch
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- when: manual
stage: "Pre Base container"
script: echo "exit 0"
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Build our base container image, which contains the core distribution, the
# toolchain, and all our build dependencies. This will be reused in the build
# stage.
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
x86_64-debian-lts-container_prep:
gitlab CI: update to recent fdo ci-templates Make use of the templating structure the templates provide. No functional changes in the end, container-build's default behavior is the previously called container-if-not-exists template. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:33:57 +03:00
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .debian-lts-x86_64
gitlab CI: update to recent fdo ci-templates Make use of the templating structure the templates provide. No functional changes in the end, container-build's default behavior is the previously called container-if-not-exists template. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2020-05-08 00:33:57 +03:00
- .fdo.container-build@debian
ci: Set timeouts on various stages Most of our stages take just a single minute to complete, while the standard timeout on gitlab CI is 60 minutes. Set a 5 minute timeout on quick stages, and a 30 minute timeout on the image build step to ensure we fail fast and don't tie up CI resources. Signed-off-by: Kenny Levinsen <kl@kl.wtf>
2021-04-15 23:43:37 +03:00
timeout: 30m
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
needs:
- job: base-container-pre
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "Base container"
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
x86_64-debian-container_prep:
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- .debian-x86_64
- .fdo.container-build@debian
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
needs:
- job: base-container-pre
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
timeout: 30m
stage: "Base container"
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
armv7-debian-lts-container_prep:
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .debian-lts-armv7
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
- .fdo.container-build@debian
tags:
- aarch64
variables:
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
FDO_BASE_IMAGE: "arm32v7/debian:$FDO_DISTRIBUTION_VERSION"
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
needs:
- job: base-container-pre
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
timeout: 30m
stage: "Base container"
armv7-debian-container_prep:
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- .debian-armv7
- .fdo.container-build@debian
tags:
- aarch64
variables:
FDO_BASE_IMAGE: "arm32v7/debian:$FDO_DISTRIBUTION_VERSION"
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
needs:
- job: base-container-pre
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
timeout: 30m
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "Base container"
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
aarch64-debian-lts-container_prep:
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .debian-lts-aarch64
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
- .fdo.container-build@debian
tags:
- aarch64
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
needs:
- job: base-container-pre
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
timeout: 30m
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "Base container"
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
aarch64-debian-container_prep:
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- .debian-aarch64
- .fdo.container-build@debian
tags:
- aarch64
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
needs:
- job: base-container-pre
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
timeout: 30m
stage: "Base container"
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Core templates for all of our build steps. These are reused by all build jobs
# through the `extends` keyword.
CI: shorten job names The old job names were really long, so long that Gitlab web UI had to almost always ellipsize them, showing only the beginning which is the same fof the two and hiding the part that actually matters. Rename the templates and the jobs to be shorter and more descriptive. Meson is the only tool we build with. All builds are native. Default options is a long way to say full-featured and besides libseat was not even default yet we build it. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-12 17:08:29 +03:00
.build-env:
ci: bump test timeouts This is prompted by the spurious CI failure https://gitlab.freedesktop.org/wayland/weston/-/jobs/13891809 saying: 31/36 output-damage TIMEOUT 122.52s 8 subtests passed 32/36 output-transforms TIMEOUT 122.52s 16 subtests passed 33/36 subsurface TIMEOUT 122.52s 34/36 xwayland TIMEOUT 122.51s 35/36 ivi-shell-app TIMEOUT 122.51s ERROR: Job failed: execution took longer than 5m0s seconds That is hitting both kinds of timeouts at the same time: the per-test timeouts, and the CI job total timeout. That run seems to have had a particularly ill fortune, as a simple retry finished the same job in 2 minutes, and the longest running test took only 24 seconds. Nevertheless, by Daniel Stone's suggestion let's bump both timeouts: - the per-test timeout to 120 seconds, which with the multiplier in CI goes up to 8 minutes - the job timeout for all build related jobs to 15 minutes The timeout for tests_standalone is not bumped as we are not adding significant amounts of new tests there. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-09-22 16:29:05 +03:00
timeout: 15m
CI: turn BUILDDIR and PREFIX into CI variables Change BUILDDIR and PREFIX from exported shell variables into CI variables. This way they can be used in CI configuration, e.g. artifacts. The main reason for this change is that it makes it possible to use these variables in after_script, which is not possible with shell variables as the values do not carry over there. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-14 13:34:49 +03:00
variables:
BUILDDIR: $CI_PROJECT_DIR/build-weston-$CI_JOB_NAME
PREFIX: $CI_PROJECT_DIR/prefix-weston-$CI_JOB_NAME
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
before_script:
CI: Deduplicate $PATH No need to set it twice. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:44:37 +03:00
- export PATH=~/.local/bin:$PATH
Add .gitlab-ci.yml Add a GitLab CI configuration which tests building, 'make check', and 'make distcheck' of the tree inside a Debian Stretch container. The choice of distribution base was arbitrary and may easily be changed. As the version of wayland-protocols available is not sufficiently new, we clone and build our own local version first. libwayland is new enough, however we could potentially reuse the artifacts generated by the Wayland CI job. When commits are pushed to upstream, the commits will run this CI pipeline to run these tests, and capture the result as an artifact bundle, including the compiled binaries and full test suite logs. Results can be seen at: https://gitlab.freedesktop.org/wayland/weston/pipelines/ Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-06-06 00:20:40 +03:00
- export XDG_RUNTIME_DIR="$(mktemp -p $(pwd) -d xdg-runtime-XXXXXX)"
gitlab CI: add support for DRM-backend tests In order to run DRM-backend tests, a DRM-device is needed. As we do not necessarily have control of the hardware that is going to run our tests in GitLab CI, DRM-backend tests were being skipped. This patch add support to run the tests using VKMS (virtual KMS). To achieve this, virtualization is needed, as we need to run a custom kernel during the CI job. We've decided to go with virtme, as it is simpler to setup and works good for our use case. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
2020-06-03 16:02:34 +03:00
- export TESTS_RES_PATH="$BUILDDIR/tests-res.txt"
Add .gitlab-ci.yml Add a GitLab CI configuration which tests building, 'make check', and 'make distcheck' of the tree inside a Debian Stretch container. The choice of distribution base was arbitrary and may easily be changed. As the version of wayland-protocols available is not sufficiently new, we clone and build our own local version first. libwayland is new enough, however we could potentially reuse the artifacts generated by the Wayland CI job. When commits are pushed to upstream, the commits will run this CI pipeline to run these tests, and capture the result as an artifact bundle, including the compiled binaries and full test suite logs. Results can be seen at: https://gitlab.freedesktop.org/wayland/weston/pipelines/ Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-06-06 00:20:40 +03:00
- mkdir "$BUILDDIR" "$PREFIX"
CI: containerize the CI Reuse the templates from wayland/ci-templates: whenever DEBIAN_TAG is changed, this will rebuild a new container. This adds two things: - better reliability (we do not randomly pull packages whenever the CI runs and we can reproduce with this particular environment) - faster builds, as we do not need to pull the universe at each run Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> [Pekka: bump DEBIAN_TAG] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-03-18 17:51:07 +03:00
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
.build-with-clang:
variables:
CI: Parameterise LLVM version Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:22:26 +03:00
CC: clang-$LLVM_VERSION
CC_LD: lld-$LLVM_VERSION
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
MESON_TOOLCHAIN_OPTIONS: "$MESON_OPTIONS -Db_lundef=false" # clang+ASan+undef=boom
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Extends the core build templates to also provide for running our testing. We
# run this inside a virtme (qemu wrapper) VM environment so we can test the DRM
# backend using the 'vkms' virtual driver under Linux.
CI: shorten job names The old job names were really long, so long that Gitlab web UI had to almost always ellipsize them, showing only the beginning which is the same fof the two and hiding the part that actually matters. Rename the templates and the jobs to be shorter and more descriptive. Meson is the only tool we build with. All builds are native. Default options is a long way to say full-featured and besides libseat was not even default yet we build it. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-12 17:08:29 +03:00
.build-and-test:
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Add Meson build This uses pip to install Meson in order to get a sufficiently new version. Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-07-22 17:38:54 +03:00
script:
- cd "$BUILDDIR"
Add support for FreeRDP 3.x With this, Weston can build against either FreeRDP 3.x or 2.x depending on what has been detected by meson (3.x takes priority). The main source of changes is the settings are now opaque and require the use of accessors. That was pretty mechanical and seems to work on 2.x as well. There are a few changes around constants getting a WINPR_ prefix, the UTF conversion functions we used are obsolete, so use the proper "new" ones, and other fairly minor things. The key & cert management changed rather completely, libfreerdp won't load files for us, we have to use the helpers to do so, and I *think* the RDP RSA key and SSL key use the same setting location. Seems to work with SSL at least. There was also a minor glitch with keyboard input, KBD_FLAGS_DOWN is basically never set. It appears to be an upstream FreeRDP change in 3.x, it was being set incorrectly (always on any key down) while it should only be set on repeats. However the fastpath input code has no way to set it from what I can tell, so it's just loss. We instead ignore it. Note that the screen size is odd (and different between freerdp client and remmina), it also won't adjust dynamically when the window is resized. I don't think this relates to my port though, I observe the same behaviour with the packaged FreeRDP 2 based Weston, but I can try to look into it later Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2024-08-02 08:45:33 +03:00
- meson --prefix="$PREFIX" --wrap-mode=nofallback -Db_sanitize=address ${MESON_OPTIONS} ${MESON_TOOLCHAIN_OPTIONS} ${MESON_DIST_OPTIONS} ..
CI: Use FDO_CI_CONCURRENT $FDO_CI_CONCURRENT is provided by in the CI environment by the fd.o GitLab runners to tell us how many parallel processes would be 'good' to use. Use this to override the default Ninja invocation which uses as many CPUs as available, and instead tell it to use as many parallel processes as the runner thinks we should during the build process. Tests are invoked using `meson test` inside a virtme/QEmu VM; whilst Meson's test backend will use as many processors as availble, virtme will by default create a single-CPU VM. So if we create a VM with as many CPUs as we should have parallel processes, we can let it use all of them. This also requires quadrupling the requested RAM so ASan doesn't force us straight into OOM. Suggested by @daenzer. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-05-18 15:56:48 +03:00
- ninja -k0 -j${FDO_CI_CONCURRENT:-4}
CI: Add Meson build This uses pip to install Meson in order to get a sufficiently new version. Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-07-22 17:38:54 +03:00
- ninja install
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
- test -n "${QEMU_SMP}" || QEMU_SMP=${FDO_CI_CONCURRENT:-4}
gitlab-ci: Use virtme-ng for running our tests virtme-ng is the an update version of virtme, and this patch uses that instead of the one we had partially modified. Besides that this partially reverts ad039cdfd2b47, 'backend-drm: Enable atomic async flip support' and makes our CI happier. Specifically ad039cdfd2b47 updated our kernel version from 6.3 to 6.9 but did not do a FDO bum,p and with that, no container images were rebuilt. Effectively we were still using 6.3. Now, with the FDO bump, in this patch, we noticed that the drm-writeback test is failing with linux kernel version 6.9. So far, only 6.3 and 6.4 kernel versions seems to be working, that is, without that drm writeback test timing out. The safest bet for the time being, would be to keep our CI just use 6.3 kernel, until we have proper version to update to. Signed-off-by: Daniel Stone <daniel.stone@collabora.com> Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-07-24 19:35:20 +03:00
- virtme-run --rw --pwd --kimg /weston-virtme/${KERNEL_IMAGE} --kopt quiet --kopt log_buf_len=2M --script-sh ../.gitlab-ci/virtme-scripts/run-weston-tests.sh --qemu-opts -m 4096 -smp ${QEMU_SMP}
gitlab CI: add support for DRM-backend tests In order to run DRM-backend tests, a DRM-device is needed. As we do not necessarily have control of the hardware that is going to run our tests in GitLab CI, DRM-backend tests were being skipped. This patch add support to run the tests using VKMS (virtual KMS). To achieve this, virtualization is needed, as we need to run a custom kernel during the CI job. We've decided to go with virtme, as it is simpler to setup and works good for our use case. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
2020-06-03 16:02:34 +03:00
- TEST_RES=$(cat $TESTS_RES_PATH)
- rm $TESTS_RES_PATH
- cp -R /weston-virtme ./
CI: Parameterise kernel build a bit more AArch64 needs different names and paths to x86-64, so let's allow for that. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:16:05 +03:00
- rm weston-virtme/${KERNEL_IMAGE}
gitlab CI: add support for DRM-backend tests In order to run DRM-backend tests, a DRM-device is needed. As we do not necessarily have control of the hardware that is going to run our tests in GitLab CI, DRM-backend tests were being skipped. This patch add support to run the tests using VKMS (virtual KMS). To achieve this, virtualization is needed, as we need to run a custom kernel during the CI job. We've decided to go with virtme, as it is simpler to setup and works good for our use case. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
2020-06-03 16:02:34 +03:00
- exit $TEST_RES
CI: Add Meson build This uses pip to install Meson in order to get a sufficiently new version. Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-07-22 17:38:54 +03:00
artifacts:
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
name: weston-$CI_COMMIT_SHA
CI: Add Meson build This uses pip to install Meson in order to get a sufficiently new version. Signed-off-by: Daniel Stone <daniels@collabora.com>
2018-07-22 17:38:54 +03:00
when: always
paths:
CI: turn BUILDDIR and PREFIX into CI variables Change BUILDDIR and PREFIX from exported shell variables into CI variables. This way they can be used in CI configuration, e.g. artifacts. The main reason for this change is that it makes it possible to use these variables in after_script, which is not possible with shell variables as the values do not carry over there. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-14 13:34:49 +03:00
- $BUILDDIR/*.png
- $BUILDDIR/meson-logs
.gitlab.ci: Enable debug for libsteat and for the DRM backend As the drm-smoke test randomly reports having the connector disabled, and with it libseat reports setMaster errors, this enables DRM backend debug messages for the kernel, and for libseat in an attempt to track down the issue, whenever it might happen again. These are pretty harmless, in terms of data being generated as we only have a single DRM test using VKMS, and the libseat debug message aren't that verbose, so we're safe keeping them for the time being. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2021-11-29 21:41:20 +03:00
- $BUILDDIR/dmesg.log
CI: turn BUILDDIR and PREFIX into CI variables Change BUILDDIR and PREFIX from exported shell variables into CI variables. This way they can be used in CI configuration, e.g. artifacts. The main reason for this change is that it makes it possible to use these variables in after_script, which is not possible with shell variables as the values do not carry over there. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-14 13:34:49 +03:00
- $BUILDDIR/weston-virtme
- $PREFIX
CI: expose test results as junit This allows Gitlab to show a detailed test report in a human friendly manner on a merge request page. The junit output depends on Meson 0.55, but Meson in CI is bumped to the latest release on Feb 15th. It is beneficial to use the newest possible Meson in CI even if we do not require it, so that we benefit from fixes, e.g. new warnings about accidentally using more recent Meson features than our minimum Meson version supports. Meson 0.57 is required for proper test names in the Gitlab report after switching the tests to TAP. See: https://github.com/mesonbuild/meson/issues/8316 Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-02-08 14:32:35 +03:00
reports:
CI: Remove per-test-asan wrapper Now that we've concluded the Xwayland/fontconfig stuff, we don't actually need a per-test wrapper; we can just set the options globally. It turns out that we don't need to set the options at all anyway, since the previous commit adds the LSan suppressions to all test runs, and LSan is enabled by default, so we can just bin it. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-06-21 15:53:45 +03:00
junit: $BUILDDIR/meson-logs/testlog-junit.xml
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Same as above, but without running any tests.
CI: shorten job names The old job names were really long, so long that Gitlab web UI had to almost always ellipsize them, showing only the beginning which is the same fof the two and hiding the part that actually matters. Rename the templates and the jobs to be shorter and more descriptive. Meson is the only tool we build with. All builds are native. Default options is a long way to say full-featured and besides libseat was not even default yet we build it. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-12 17:08:29 +03:00
.build-no-test:
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
gitlab-ci.yml: Have a doc job This helps identify if we have actually have a build issue or if we have a documentation build failure. Notifications sent out are specifying the name of the build, making things much easier to figure out what actually failed. Uses another job w/o the need to run the tests (again). Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2020-12-02 23:30:34 +03:00
script:
- cd "$BUILDDIR"
Add support for FreeRDP 3.x With this, Weston can build against either FreeRDP 3.x or 2.x depending on what has been detected by meson (3.x takes priority). The main source of changes is the settings are now opaque and require the use of accessors. That was pretty mechanical and seems to work on 2.x as well. There are a few changes around constants getting a WINPR_ prefix, the UTF conversion functions we used are obsolete, so use the proper "new" ones, and other fairly minor things. The key & cert management changed rather completely, libfreerdp won't load files for us, we have to use the helpers to do so, and I *think* the RDP RSA key and SSL key use the same setting location. Seems to work with SSL at least. There was also a minor glitch with keyboard input, KBD_FLAGS_DOWN is basically never set. It appears to be an upstream FreeRDP change in 3.x, it was being set incorrectly (always on any key down) while it should only be set on repeats. However the fastpath input code has no way to set it from what I can tell, so it's just loss. We instead ignore it. Note that the screen size is odd (and different between freerdp client and remmina), it also won't adjust dynamically when the window is resized. I don't think this relates to my port though, I observe the same behaviour with the packaged FreeRDP 2 based Weston, but I can try to look into it later Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2024-08-02 08:45:33 +03:00
- meson --prefix="$PREFIX" --wrap-mode=nofallback ${MESON_OPTIONS} ${MESON_DIST_OPTIONS} ..
CI: Use FDO_CI_CONCURRENT $FDO_CI_CONCURRENT is provided by in the CI environment by the fd.o GitLab runners to tell us how many parallel processes would be 'good' to use. Use this to override the default Ninja invocation which uses as many CPUs as available, and instead tell it to use as many parallel processes as the runner thinks we should during the build process. Tests are invoked using `meson test` inside a virtme/QEmu VM; whilst Meson's test backend will use as many processors as availble, virtme will by default create a single-CPU VM. So if we create a VM with as many CPUs as we should have parallel processes, we can let it use all of them. This also requires quadrupling the requested RAM so ASan doesn't force us straight into OOM. Suggested by @daenzer. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-05-18 15:56:48 +03:00
- ninja -k0 -j${FDO_CI_CONCURRENT:-4}
gitlab-ci.yml: Have a doc job This helps identify if we have actually have a build issue or if we have a documentation build failure. Notifications sent out are specifying the name of the build, making things much easier to figure out what actually failed. Uses another job w/o the need to run the tests (again). Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2020-12-02 23:30:34 +03:00
- ninja install
- ninja clean
artifacts:
name: weston-$CI_COMMIT_SHA
when: always
paths:
CI: turn BUILDDIR and PREFIX into CI variables Change BUILDDIR and PREFIX from exported shell variables into CI variables. This way they can be used in CI configuration, e.g. artifacts. The main reason for this change is that it makes it possible to use these variables in after_script, which is not possible with shell variables as the values do not carry over there. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-14 13:34:49 +03:00
- $BUILDDIR/meson-logs
- $PREFIX
gitlab-ci.yml: Have a doc job This helps identify if we have actually have a build issue or if we have a documentation build failure. Notifications sent out are specifying the name of the build, making things much easier to figure out what actually failed. Uses another job w/o the need to run the tests (again). Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2020-12-02 23:30:34 +03:00
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
# OS/architecture-specific variants
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.build-env-debian-lts-x86_64:
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .debian-lts-x86_64
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
- .fdo.suffixed-image@debian
- .build-env
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
needs:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- job: x86_64-debian-lts-container_prep
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
artifacts: false
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.build-env-debian-x86_64:
extends:
- .debian-x86_64
- .fdo.suffixed-image@debian
- .build-env
needs:
- job: x86_64-debian-container_prep
artifacts: false
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.build-env-debian-lts-armv7:
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
tags:
- aarch64
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .debian-lts-armv7
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
- .fdo.suffixed-image@debian
- .build-env
needs:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- job: armv7-debian-lts-container_prep
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
artifacts: false
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.build-env-debian-armv7:
tags:
- aarch64
extends:
- .debian-armv7
- .fdo.suffixed-image@debian
- .build-env
needs:
- job: armv7-debian-container_prep
artifacts: false
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.build-env-debian-lts-aarch64:
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
tags:
- aarch64
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .debian-lts-aarch64
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
- .fdo.suffixed-image@debian
- .build-env
needs:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- job: aarch64-debian-lts-container_prep
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
artifacts: false
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.build-env-debian-aarch64:
tags:
- aarch64
extends:
- .debian-aarch64
- .fdo.suffixed-image@debian
- .build-env
needs:
- job: aarch64-debian-container_prep
artifacts: false
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.test-env-debian-lts-x86_64:
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
tags:
- kvm
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .build-env-debian-lts-x86_64
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
- .build-and-test
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
needs:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- job: x86_64-debian-lts-container_prep
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
artifacts: false
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.test-env-debian-x86_64:
tags:
- kvm
extends:
- .build-env-debian-x86_64
- .build-and-test
needs:
- job: x86_64-debian-container_prep
artifacts: false
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
.test-env-debian-lts-aarch64:
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
tags:
- kvm-aarch64
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .build-env-debian-lts-aarch64
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
- .build-and-test
needs:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- job: aarch64-debian-lts-container_prep
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
artifacts: false
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
.test-env-debian-aarch64:
tags:
- kvm-aarch64
extends:
- .build-env-debian-aarch64
- .build-and-test
needs:
- job: aarch64-debian-container_prep
artifacts: false
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
# Full build, used for testing under KVM.
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
.build-options-full:
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "Full build and test"
gitlab-ci: add build configuration without gl-renderer Building without gl-renderer seems to fail rather often. Introduce a specific build job which tests this configuration. Make use of the Folded Block Scalar in YAML to concatenate the build option string with spaces. This will make diffing build option changes very readable. Signed-off-by: Stefan Agner <stefan@agner.ch>
2019-10-20 18:19:03 +03:00
variables:
MESON_OPTIONS: >
CI: add test coverage results This runs the coverage tools to produce HTML pages listing the code lines / functions / branches hit/totalled by the test suite. Nowadays Gitlab has some Cobertura support itself: https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html lcov is needed for the HTML report, gcovr is needed for the Cobertura report. 'ninja clean' must be removed, otherwise it deletes the coverage files before they are analysed. Seeing the test suite code coverage is really interesting. It can guide designing tests. If Gitlab MRs show the coverage in diff view, it shows if new code actually gets executed in CI. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-21 16:06:30 +03:00
-Doptimization=0
-Db_coverage=true
gitlab-ci: add build configuration without gl-renderer Building without gl-renderer seems to fail rather often. Introduce a specific build job which tests this configuration. Make use of the Folded Block Scalar in YAML to concatenate the build option string with spaces. This will make diffing build option changes very readable. Signed-off-by: Stefan Agner <stefan@agner.ch>
2019-10-20 18:19:03 +03:00
-Dwerror=true
CI: test skips are failures In CI we should never get a skip, so turn them into failures to make sure we notice. This is enabled only for the configuration where we build everything. If anything is disabled, skips are expected. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-03-03 15:31:54 +03:00
-Dtest-skip-is-failure=true
CI: add test coverage results This runs the coverage tools to produce HTML pages listing the code lines / functions / branches hit/totalled by the test suite. Nowadays Gitlab has some Cobertura support itself: https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html lcov is needed for the HTML report, gcovr is needed for the Cobertura report. 'ninja clean' must be removed, otherwise it deletes the coverage files before they are analysed. Seeing the test suite code coverage is really interesting. It can guide designing tests. If Gitlab MRs show the coverage in diff view, it shows if new code actually gets executed in CI. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-21 16:06:30 +03:00
after_script:
CI: put coverage-html output into file I'm tired of scrolling through that flood when looking at CI logs. It's just listing every gcno, gcda and c file name as it parses them. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-12 14:44:17 +03:00
- ninja -C "$BUILDDIR" coverage-html > "$BUILDDIR/meson-logs/ninja-coverage-html.txt"
CI: turn BUILDDIR and PREFIX into CI variables Change BUILDDIR and PREFIX from exported shell variables into CI variables. This way they can be used in CI configuration, e.g. artifacts. The main reason for this change is that it makes it possible to use these variables in after_script, which is not possible with shell variables as the values do not carry over there. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-05-14 13:34:49 +03:00
- ninja -C "$BUILDDIR" coverage-xml
gitlab-ci: add build configuration without gl-renderer Building without gl-renderer seems to fail rather often. Introduce a specific build job which tests this configuration. Make use of the Folded Block Scalar in YAML to concatenate the build option string with spaces. This will make diffing build option changes very readable. Signed-off-by: Stefan Agner <stefan@agner.ch>
2019-10-20 18:19:03 +03:00
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
x86_64-debian-lts-full-build:
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .test-env-debian-lts-x86_64
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
- .build-options-full
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
x86_64-debian-full-build:
extends:
- .test-env-debian-x86_64
- .build-options-full
CI: emit cobertura artifact from only one job I do not know what happens if multiple jobs declare artifacts:reports:cobertura. Maybe the last job to finish wins? Who cares, Gitlab can only show the results from one cobertura report in the MR diff view. Recently, the MR diffs have the coverage annotations, but there was a time when they seemed to be missing. I don't know why. Let's make sure the cobertura report Gitlab will use is from the "main" build only: 64-bit Debian with full features and gcc. I do not move the after_script, because maybe someone could have a reason to look at arch-specific coverage reports, so I want to leave the HTML there in the artifacts. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-12-02 16:51:55 +03:00
artifacts:
reports:
ci: Fix cobertura syntax This has somehow stopped working. Copied different syntax from a gitlab example. Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
2022-06-06 21:56:19 +03:00
coverage_report:
coverage_format: cobertura
path: $BUILDDIR/meson-logs/coverage.xml
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
aarch64-debian-lts-full-build:
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .test-env-debian-lts-aarch64
CI: Add full AArch64 KVM support Build a kernel for AArch64 and run it under virtme just like we do for x86-64. This requires adding support for the AArch64 defconfig variant, and accommodating for the fact that it builds DRM as a module by default rather than built in. The virtme branch we are using has also been rebased on top of newer virtme upstream which unbreaks AArch64. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:33:01 +03:00
- .build-options-full
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
aarch64-debian-full-build:
extends:
- .test-env-debian-aarch64
- .build-options-full
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
x86_64-clang-debian-lts-full-build:
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .test-env-debian-lts-x86_64
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
- .build-with-clang
- .build-options-full
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
x86_64-clang-debian-full-build:
extends:
- .test-env-debian-x86_64
- .build-with-clang
- .build-options-full
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
aarch64-clang-debian-lts-full-build:
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .test-env-debian-lts-aarch64
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
- .build-with-clang
- .build-options-full
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
aarch64-clang-debian-full-build:
extends:
- .test-env-debian-aarch64
- .build-with-clang
- .build-options-full
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
# Docs should be invariant on all architectures, so we only do it on Debian
# x86-64.
CI: Rename job names to keep parameters first GitLab already groups our various stages (container, build, etc) into separate UI elements. Within those stages, the important information is the parameterisation (architecture, OS, toolchain). We don't want that to get ellipsised, so put that first in the job names. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:38:06 +03:00
docs-build:
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "Other builds"
gitlab-ci.yml: Have a doc job This helps identify if we have actually have a build issue or if we have a documentation build failure. Notifications sent out are specifying the name of the build, making things much easier to figure out what actually failed. Uses another job w/o the need to run the tests (again). Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2020-12-02 23:30:34 +03:00
variables:
MESON_OPTIONS: >
-Dwerror=true
-Ddoc=true
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
extends:
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- .build-env-debian-x86_64
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
- .build-no-test
gitlab-ci.yml: Have a doc job This helps identify if we have actually have a build issue or if we have a documentation build failure. Notifications sent out are specifying the name of the build, making things much easier to figure out what actually failed. Uses another job w/o the need to run the tests (again). Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2020-12-02 23:30:34 +03:00
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
# Building without gl-renderer, to make sure this keeps working.
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
.build-options-no-gl:
CI: Separate build types out into stages Give ourselves a bit more separation between the different job types, so it's easier to see what's running and/or failing. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 12:58:39 +03:00
stage: "No-GL build and test"
gitlab-ci: add build configuration without gl-renderer Building without gl-renderer seems to fail rather often. Introduce a specific build job which tests this configuration. Make use of the Folded Block Scalar in YAML to concatenate the build option string with spaces. This will make diffing build option changes very readable. Signed-off-by: Stefan Agner <stefan@agner.ch>
2019-10-20 18:19:03 +03:00
variables:
MESON_OPTIONS: >
-Dsimple-clients=damage,im,shm,touch,dmabuf-v4l
-Drenderer-gl=false
-Dremoting=false
backend-drm: build DRM virtual support when the pipewire plugin is enabled The pipewire plugin uses this API as well, not just the remoting plugin. So enable it if either is enabled. And disable pipewire in the no-gl-renderer CI build. The virtual outputs don't work without it. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
2020-07-15 12:01:04 +03:00
-Dpipewire=false
gitlab-ci: add build configuration without gl-renderer Building without gl-renderer seems to fail rather often. Introduce a specific build job which tests this configuration. Make use of the Folded Block Scalar in YAML to concatenate the build option string with spaces. This will make diffing build option changes very readable. Signed-off-by: Stefan Agner <stefan@agner.ch>
2019-10-20 18:19:03 +03:00
-Dwerror=true
ci: upgrade seatd to 0.6 This upgrades seatd to the latest version. Examples are disabled by default. Man pages are already disabled by auto_features=disabled. Other build options have been renamed. Signed-off-by: Simon Ser <contact@emersion.fr>
2021-09-12 14:48:41 +03:00
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
x86_64-debian-lts-no-gl-build:
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .test-env-debian-lts-x86_64
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
- .build-options-no-gl
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
x86_64-debian-no-gl-build:
extends:
- .test-env-debian-x86_64
- .build-options-no-gl
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
armv7-debian-lts-no-gl-build:
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .build-env-debian-lts-armv7
CI: Add ARMv7 support ARMv7 is still an important architecture for us to run on, and running on ARMv7 also gives us 32-bit build coverage. As distros are deprecating their non-64-bit-x86 support, this may be our only realistic chance of ensuring that our build is also 32-bit-clean. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:53:07 +03:00
- .build-no-test
- .build-options-no-gl
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
armv7-debian-no-gl-build:
extends:
- .build-env-debian-armv7
- .build-no-test
- .build-options-no-gl
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
armv7-clang-debian-lts-no-gl-build:
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .build-env-debian-lts-armv7
ci: Add clang build jobs Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-08-03 15:11:51 +03:00
- .build-with-clang
- .build-no-test
- .build-options-no-gl
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
armv7-clang-debian-no-gl-build:
extends:
- .build-env-debian-armv7
- .build-with-clang
- .build-no-test
- .build-options-no-gl
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
aarch64-debian-lts-no-gl-build:
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
extends:
CI: Rename debian jobs to debian-lts Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 14:25:16 +03:00
- .test-env-debian-lts-aarch64
CI: Add initial AArch64 support This only runs a single build job, to build without GL and not run any tests, as KVM support is not yet included. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:22:49 +03:00
- .build-options-no-gl
gitlab-ci: add build configuration without gl-renderer Building without gl-renderer seems to fail rather often. Introduce a specific build job which tests this configuration. Make use of the Folded Block Scalar in YAML to concatenate the build option string with spaces. This will make diffing build option changes very readable. Signed-off-by: Stefan Agner <stefan@agner.ch>
2019-10-20 18:19:03 +03:00
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
aarch64-debian-no-gl-build:
extends:
- .test-env-debian-aarch64
- .build-options-no-gl
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Expose docs and coverage reports, so we can show users any changes to these
# inside their merge requests, letting us check them before merge.
#
# This does not build the docs or coverage information itself, but just reuses
# the docs and coverage information from the x86-64 Debian builds as the
# canonical sources of coverage information; the docs themselves should be
# invariant across any architecture or OS.
CI: add test coverage results This runs the coverage tools to produce HTML pages listing the code lines / functions / branches hit/totalled by the test suite. Nowadays Gitlab has some Cobertura support itself: https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html lcov is needed for the HTML report, gcovr is needed for the Cobertura report. 'ninja clean' must be removed, otherwise it deletes the coverage files before they are analysed. Seeing the test suite code coverage is really interesting. It can guide designing tests. If Gitlab MRs show the coverage in diff view, it shows if new code actually gets executed in CI. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-21 16:06:30 +03:00
docs-and-coverage:
ci: Fix pull rate limit errors Pull the container from a source without a rate limit Suggested by Daniel Stone <daniels@collabora.com> Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
2021-07-28 18:54:19 +03:00
extends:
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
- .default-rules
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- .debian-x86_64
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
- .fdo.suffixed-image@debian
CI: expose built docs preview This adds a link in any MR to the documentation from the CI build, making it easy to preview the documentation. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-26 15:14:58 +03:00
stage: pages
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
needs:
- job: docs-build
artifacts: true
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- job: x86_64-debian-full-build
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
artifacts: true
ci: Set timeouts on various stages Most of our stages take just a single minute to complete, while the standard timeout on gitlab CI is 60 minutes. Set a 5 minute timeout on quick stages, and a 30 minute timeout on the image build step to ensure we fail fast and don't tie up CI resources. Signed-off-by: Kenny Levinsen <kl@kl.wtf>
2021-04-15 23:43:37 +03:00
timeout: 5m
CI: expose built docs preview This adds a link in any MR to the documentation from the CI build, making it easy to preview the documentation. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-26 15:14:58 +03:00
script:
CI: Rename job names to keep parameters first GitLab already groups our various stages (container, build, etc) into separate UI elements. Within those stages, the important information is the parameterisation (architecture, OS, toolchain). We don't want that to get ellipsised, so put that first in the job names. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:38:06 +03:00
- mv prefix-weston-docs-build/share/doc/weston Documentation
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- mv build-weston-x86_64-debian-full-build/meson-logs/coveragereport Test_Coverage
CI: a new style for LCOV reports The standard style of LCOV HTML reports is a bit harsh to look at. This commit replaces it with a new one. The new CSS was written from scratch by looking at the HTML source code of a generated LCOV report. The original gcov.css file was not used. The color scheme is neutral, trying to avoid a Christmas tree effect. The colors are intended to be calm while also distinguishable, and not hamper text readability. The font lists were taken from Gitlab with the hope that it will blend in a little better when viewing from MR artifacts. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-03-15 12:20:17 +03:00
- rm Test_Coverage/gcov.css
- cp doc/style/lcov-style.css Test_Coverage/gcov.css
- cp doc/style/*.png Test_Coverage/
CI: expose built docs preview This adds a link in any MR to the documentation from the CI build, making it easy to preview the documentation. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-26 15:14:58 +03:00
- rm -rf build-* prefix-*
artifacts:
CI: add test coverage results This runs the coverage tools to produce HTML pages listing the code lines / functions / branches hit/totalled by the test suite. Nowadays Gitlab has some Cobertura support itself: https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html lcov is needed for the HTML report, gcovr is needed for the Cobertura report. 'ninja clean' must be removed, otherwise it deletes the coverage files before they are analysed. Seeing the test suite code coverage is really interesting. It can guide designing tests. If Gitlab MRs show the coverage in diff view, it shows if new code actually gets executed in CI. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-21 16:06:30 +03:00
expose_as: 'Documentation preview and test coverage report'
CI: expose built docs preview This adds a link in any MR to the documentation from the CI build, making it easy to preview the documentation. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-26 15:14:58 +03:00
paths:
- Documentation/
CI: add test coverage results This runs the coverage tools to produce HTML pages listing the code lines / functions / branches hit/totalled by the test suite. Nowadays Gitlab has some Cobertura support itself: https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html lcov is needed for the HTML report, gcovr is needed for the Cobertura report. 'ninja clean' must be removed, otherwise it deletes the coverage files before they are analysed. Seeing the test suite code coverage is really interesting. It can guide designing tests. If Gitlab MRs show the coverage in diff view, it shows if new code actually gets executed in CI. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-21 16:06:30 +03:00
- Test_Coverage/
CI: expose built docs preview This adds a link in any MR to the documentation from the CI build, making it easy to preview the documentation. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2019-11-26 15:14:58 +03:00
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# Generate the documentation for https://wayland.pages.freedesktop.org/weston/
# Anything under public/ is published to this URL.
#
gitlab-ci.yml: Avoid running CI for merge pipelines This avoids running pipelines *after* the MR has been merged and avoids triggering a new CI build and with it the tests. These should already be done in the MR context so there's no need to run them once more time. Further more, with this change forks would need to manually trigger builds. No change for the MR context, as these it would build automatically. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-07 15:45:17 +03:00
# Does not inherit .default-rules as it should only run in our default branch for
CI: Document the build and container process Explain what we do within our CI and why, with links as required. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:34:43 +03:00
# the upstream repo.
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
pages:
gitlab-ci.yml: Use same container source as the docs Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2021-07-28 21:42:52 +03:00
extends:
CI: Add Debian bookworm jobs Bookworm has just been released. Add jobs which start using it, but keep bullseye around as the LTS release, to make sure we can build on new and old distributions. Signed-off-by: Daniel Stone <daniels@collabora.com>
2023-05-17 15:43:20 +03:00
- .debian-x86_64
CI: Start parameterising for OS/architecture No functional change to the test runs, apart from changing the job names. This will allow us to test along more axes without more duplication. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 00:25:41 +03:00
- .fdo.suffixed-image@debian
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
stage: pages
ci: Set timeouts on various stages Most of our stages take just a single minute to complete, while the standard timeout on gitlab CI is 60 minutes. Set a 5 minute timeout on quick stages, and a 30 minute timeout on the image build step to ensure we fail fast and don't tie up CI resources. Signed-off-by: Kenny Levinsen <kl@kl.wtf>
2021-04-15 23:43:37 +03:00
timeout: 5m
CI: Use 'needs' to make dependencies more clear GitLab CI has two execution scheduling models. The original model is to split jobs into stages; jobs within a single stage may execute in parallel, but execution is serialised between stages. As we move to supporting multiple OSes and architectures, there is no need to serialise, e.g. the AArch64 Linux build against the x86-64 FreeBSD container preparation. Declare our dependencies explicitly using `needs`. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-22 02:08:20 +03:00
needs:
- job: docs-build
artifacts: true
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
script:
CI: Rename job names to keep parameters first GitLab already groups our various stages (container, build, etc) into separate UI elements. Within those stages, the important information is the parameterisation (architecture, OS, toolchain). We don't want that to get ellipsised, so put that first in the job names. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-06-21 23:38:06 +03:00
- export PREFIX=$(pwd)/prefix-weston-docs-build
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
- mkdir public
gitlab-ci: Fix pages generation for the documentation Fixes 0a13641ff: "gitlab-ci: Enable gitlab page for publishing documentation", to point to correct sphinx documentation. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-25 17:17:08 +03:00
- cp -R $PREFIX/share/doc/weston/* public/
gitlab-ci: Enable gitlab page for publishing documentation While adding pages, remove CI_JOB_ID and CI_JOB_SHA from PREFIX, as this apparently is not needed. Make build-native-meson a dependency for the pages stage. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2019-06-14 16:00:07 +03:00
artifacts:
paths:
- public
ci: Switch to using new rules syntax The rules syntax is more clear and explicit than the previous only/except. Switch to using that. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-07-31 17:11:35 +03:00
rules:
gitlab-ci.yml: Update CI_BUILD_REF_NAME With GitLab 16.0 CI_BUILD_REF_NAME was replaced with CI_COMMIT_REF_NAME. which might explain why we do not seem to install the documentation on https://wayland.pages.freedesktop.org/weston/ This should makes that docs deplay stage run. Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
2024-06-05 13:35:06 +03:00
- if: '$CI_PIPELINE_SOURCE == "push" && $CI_PROJECT_PATH == "wayland/weston" && $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH'
ci: Switch to using new rules syntax The rules syntax is more clear and explicit than the previous only/except. Switch to using that. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-07-31 17:11:35 +03:00
when: on_success
- when: never