mirrors/weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3459bad63d
weston/.gitlab-ci.yml

172 lines
4.0 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:
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: 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:
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'
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
ref: 59de540b620c45739871d1a073d76d5521989d11
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'
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: 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
- container_prep
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
- 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
- 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
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
.debian:
variables:
FDO_DISTRIBUTION_VERSION: buster
FDO_DISTRIBUTION_EXEC: 'bash .gitlab-ci/debian-install.sh'
ci: Build with libseat enabled This installs libseat in the debian image build from source in order to enable, build and test weston with libseat support. Signed-off-by: Kenny Levinsen <kl@kl.wtf>
2021-04-14 23:37:36 +03:00
FDO_DISTRIBUTION_TAG: '2021-04-15.2'
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: 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
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:
- .debian
- .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
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
stage: container_prep
.build-native:
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:
- .debian
- .fdo.distribution-image@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: 5m
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
stage: build
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:
gitlab-ci: Use gitlab.fdo URL for wayland-protocols Signed-off-by: Harish Krupo <harishkrupo@gmail.com>
2019-05-09 12:56:04 +03:00
- git clone --depth=1 https://gitlab.freedesktop.org/wayland/wayland-protocols
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 WAYLAND_PROTOCOLS_DIR="$(pwd)/prefix-wayland-protocols"
- export PKG_CONFIG_PATH="$WAYLAND_PROTOCOLS_DIR/share/pkgconfig:$PKG_CONFIG_PATH"
- export MAKEFLAGS="-j4"
- cd wayland-protocols
- git show -s HEAD
- mkdir build
- cd build
- ../autogen.sh --prefix="$WAYLAND_PROTOCOLS_DIR"
- make install
- cd ../../
- export XDG_RUNTIME_DIR="$(mktemp -p $(pwd) -d xdg-runtime-XXXXXX)"
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
- export BUILD_ID="weston-$CI_JOB_NAME"
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 PREFIX="$(pwd)/prefix-$BUILD_ID"
- export BUILDDIR="$(pwd)/build-$BUILD_ID"
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
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
.build-native-meson:
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
extends: .build-native
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
tags:
- kvm
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:
- export PATH=~/.local/bin:$PATH
- cd "$BUILDDIR"
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
- meson --prefix="$PREFIX" ${MESON_OPTIONS} ..
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 -k0
- ninja install
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
- virtme-run --rw --pwd --kimg /weston-virtme/bzImage --script-dir ../.gitlab-ci/virtme-scripts
- TEST_RES=$(cat $TESTS_RES_PATH)
- rm $TESTS_RES_PATH
- cp -R /weston-virtme ./
- rm weston-virtme/bzImage
- 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: store test images in artifacts If a screenshooting test fails, it quite likely writes not only the screenshot but also a diff image highlighting the failed pixels. These would be good to have in the CI artifacts for postmortem. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2020-03-02 16:05:08 +03:00
- build-*/*.png
gitlab-ci: Actually capture Meson logs Correct the path to the build directory so we can capture Meson logs; especially useful when tests fail like in #184. An example of this change having been run with a deliberately-failing test, capturing the Meson logs, can be found at: https://gitlab.freedesktop.org/daniels/weston/-/jobs/94623 Signed-off-by: Daniel Stone <daniels@collabora.com>
2019-01-31 05:06:22 +03:00
- build-*/meson-logs
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
- build-*/weston-virtme
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
- 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:
junit: build-*/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
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
.build-native-meson-no-test:
extends: .build-native
tags:
- kvm
script:
- export PATH=~/.local/bin:$PATH
- cd "$BUILDDIR"
- meson --prefix="$PREFIX" ${MESON_OPTIONS} ..
- ninja -k0
- ninja install
- ninja clean
artifacts:
name: weston-$CI_COMMIT_SHA
when: always
paths:
- build-*/meson-logs
- prefix-*
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
build-native-meson-default-options:
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: Build with libseat enabled This installs libseat in the debian image build from source in order to enable, build and test weston with libseat support. Signed-off-by: Kenny Levinsen <kl@kl.wtf>
2021-04-14 23:37:36 +03:00
-Dlauncher-libseat=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
extends: .build-native-meson
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:
- ninja -C build-* coverage-html
- ninja -C build-* coverage-xml
CI: work around Gitlab Cobertura parsing quirk This should not be necessary, but my testing with fd.o Gitlab 13.9.1 shows this is needed. Otherwise the coverage markings will not appear in a MR diff view. Apparently Gitlab has some problem with 'filename' attribute containing "../" in Cobertura XML files, even when that does result in a correct path. Or maybe the problem is is with the <source> path referring to the build dir which from Gitlab perspective does not exist in the project, even though builddir/../ is a good path. This sed hack removes the "../" part and the last element in the <source> path correspondingly. See https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/567 for my testing. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2021-03-04 18:35:09 +03:00
- sed -i -e 's/\/build-weston-build-native-meson-default-options//' -e 's/\"..\//\"/' build-*/meson-logs/coverage.xml
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
artifacts:
reports:
cobertura: build-*/meson-logs/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
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
build-docs:
variables:
MESON_OPTIONS: >
-Dwerror=true
-Ddoc=true
extends: .build-native-meson-no-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
build-native-meson-no-gl-renderer:
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: Build with libseat enabled This installs libseat in the debian image build from source in order to enable, build and test weston with libseat support. Signed-off-by: Kenny Levinsen <kl@kl.wtf>
2021-04-14 23:37:36 +03:00
-Dlauncher-libseat=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
extends: .build-native-meson
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: 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: 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:
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
- mv prefix-weston-build-docs/share/doc/weston 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
- mv build-weston-build-native-meson-default-options/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-*
dependencies:
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
- build-docs
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
- build-native-meson-default-options
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
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
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:
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
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
dependencies:
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
- build-docs
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:
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
- export PREFIX=$(pwd)/prefix-weston-build-docs
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
only:
CI: Run Pages build on main Predictably, there was one thing I forgot with !600, which was to fix up the CI rules for the transition. Oops. Signed-off-by: Daniel Stone <daniels@collabora.com>
2021-04-27 20:54:13 +03:00
- main
Reference in New Issue Copy Permalink