mainnika
/
weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7501 Commits
1 Branch
0 Tags
13 MiB
Tag: Branch: Tree: 7ae8a89a8b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7ae8a89a8b'
${ noResults }
weston/.gitlab-ci.yml

172 lines
4.1 KiB
Raw Normal View History Unescape

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>
6 years ago
# 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>
5 years ago
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>
6 years ago
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>
5 years ago
- 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>
5 years ago
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>
6 years ago
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>
7 years ago
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>
6 years ago
- 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>
7 years ago
- 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>
5 years ago
- 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>
7 years ago
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>
5 years ago
.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>
4 years ago
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>
5 years ago
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>
6 years ago
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>
5 years ago
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>
4 years ago
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>
6 years ago
stage: container_prep
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>
4 years ago
.build-env:
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>
5 years ago
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>
4 years ago
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>
7 years ago
stage: build
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>
4 years ago
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>
6 years ago
before_script:
gitlab-ci: Use gitlab.fdo URL for wayland-protocols Signed-off-by: Harish Krupo <harishkrupo@gmail.com>
6 years ago
- 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>
7 years ago
- export WAYLAND_PROTOCOLS_DIR="$(pwd)/prefix-wayland-protocols"
- export PKG_CONFIG_PATH="$WAYLAND_PROTOCOLS_DIR/share/pkgconfig:$PKG_CONFIG_PATH"
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>
4 years ago
- export MAKEFLAGS="-j${FDO_CI_CONCURRENT:-4}"
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>
7 years ago
- 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: 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>
5 years ago
- 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>
7 years ago
- 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>
6 years ago
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>
4 years ago
.build-and-test:
extends: .build-env
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>
5 years ago
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>
6 years ago
script:
- export PATH=~/.local/bin:$PATH
- cd "$BUILDDIR"
CI: use address sanitizer without leak checks Use address sanitizer to catch use-after-free and other errors when running the test suite. Leak detection is disabled, because currently there are too many leaks, making almost all tests fail otherwise. The atexit=1 is for verifying that ASan was actually used. The default 128 MB of RAM in the qemu machine leads to oom-killer killing most tests, so bump the memory size to 1 GB. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
4 years ago
- meson --prefix="$PREFIX" -Db_sanitize=address ${MESON_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>
4 years ago
- 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>
6 years ago
- ninja install
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>
4 years ago
- virtme-run --rw --pwd --kimg /weston-virtme/bzImage --kopt quiet --script-dir ../.gitlab-ci/virtme-scripts --qemu-opts -m 4096 -smp ${FDO_CI_CONCURRENT:-4}
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>
5 years ago
- 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>
6 years ago
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>
5 years ago
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>
6 years ago
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>
4 years ago
- $BUILDDIR/*.png
- $BUILDDIR/meson-logs
- $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>
4 years ago
reports:
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>
4 years ago
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>
5 years ago
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>
4 years ago
.build-no-test:
extends: .build-env
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>
4 years ago
tags:
- kvm
script:
- export PATH=~/.local/bin:$PATH
- cd "$BUILDDIR"
- meson --prefix="$PREFIX" ${MESON_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>
4 years ago
- 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>
4 years ago
- 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>
4 years ago
- $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>
4 years ago
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>
4 years ago
build-full:
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>
5 years ago
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>
5 years ago
-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>
5 years ago
-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>
4 years ago
-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>
4 years ago
-Dlauncher-libseat=true
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>
4 years ago
extends: .build-and-test
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>
5 years ago
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>
4 years ago
- 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>
4 years ago
- ninja -C "$BUILDDIR" coverage-xml
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>
4 years ago
- sed -i -e 's/\/build-weston-build-full//' -e 's/\"..\//\"/' "$BUILDDIR/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>
5 years ago
artifacts:
reports:
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>
4 years ago
cobertura: $BUILDDIR/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>
5 years ago
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>
4 years ago
build-docs:
variables:
MESON_OPTIONS: >
-Dwerror=true
-Ddoc=true
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>
4 years ago
extends: .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>
4 years ago
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>
4 years ago
build-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>
5 years ago
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>
4 years ago
-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>
5 years ago
-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>
4 years ago
-Dlauncher-libseat=true
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>
4 years ago
extends: .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>
5 years ago
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>
5 years ago
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>
5 years ago
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>
4 years ago
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>
5 years ago
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>
4 years ago
- mv prefix-weston-build-docs/share/doc/weston Documentation
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>
4 years ago
- mv build-weston-build-full/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>
4 years ago
- 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>
5 years ago
- 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>
4 years ago
- build-docs
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>
4 years ago
- build-full
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>
5 years ago
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>
5 years ago
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>
5 years ago
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>
5 years ago
- 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>
5 years ago
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>
5 years ago
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>
4 years ago
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>
5 years ago
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>
4 years ago
- 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>
5 years ago
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>
4 years ago
- 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>
5 years ago
- 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>
5 years ago
- 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>
5 years ago
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>
4 years ago
- main