isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-21 15:40:41 -05:00
Code Issues Packages Projects Releases Wiki Activity
1fd53c480f
mutter/.gitlab-ci.yml

94 lines
2.1 KiB
YAML
Raw Normal View History

ci: Update docker image to v3 It's this time of the cycle again: Rebase the docker image to the upcoming Fedora release, so we can drop a fair bit of the custom dependencies that have piled up. https://gitlab.gnome.org/GNOME/mutter/merge_requests/894
2019-10-28 19:50:07 -04:00
image: registry.gitlab.gnome.org/gnome/mutter/master:v3
Add .gitlab-ci.yml for build testing This adds compilation testing using meson on the gitlab instance. It uses a prebuild image built, described in .gitlab-ci/Dockerfile, based on Fedora 29. The image is build and published by running: cd .gitlab-ci/ docker build -t registry.gitlab.gnome.org/gnome/mutter/master:v1 . docker push registry.gitlab.gnome.org/gnome/mutter/master:v1 Resolves: https://gitlab.gnome.org/GNOME/mutter/merge_requests/132
2018-06-14 15:01:35 -04:00
stages:
gitlab-ci.yml: Add check for issue or MR URL This adds a pipeline stage for merge requests that checks that the commit message contains an URL to either a issue or a merge request. This means that for merge requests without corresponding issues will always fail initially, as the merge request URL is not known until after it is created. This is still arguably better than accidentally merging merge requests without URLs. https://gitlab.gnome.org/GNOME/mutter/merge_requests/440
2019-02-05 12:19:43 -05:00
- review
Add .gitlab-ci.yml for build testing This adds compilation testing using meson on the gitlab instance. It uses a prebuild image built, described in .gitlab-ci/Dockerfile, based on Fedora 29. The image is build and published by running: cd .gitlab-ci/ docker build -t registry.gitlab.gnome.org/gnome/mutter/master:v1 . docker push registry.gitlab.gnome.org/gnome/mutter/master:v1 Resolves: https://gitlab.gnome.org/GNOME/mutter/merge_requests/132
2018-06-14 15:01:35 -04:00
- build
gitlab-ci: Add test stage The test stage runs the whole meson test suite inside Xvfb inside a dbus session. Running inside Xvfb is required as the cogl, clutter and mutter tests require to run on top of X11; the dbus session is required to make mutter succeed in owning names on the bus. This also updates the Dockerfile to include packages needed for running tests. https://gitlab.gnome.org/GNOME/mutter/issues/193
2018-08-17 08:15:29 -04:00
- test
Add .gitlab-ci.yml for build testing This adds compilation testing using meson on the gitlab instance. It uses a prebuild image built, described in .gitlab-ci/Dockerfile, based on Fedora 29. The image is build and published by running: cd .gitlab-ci/ docker build -t registry.gitlab.gnome.org/gnome/mutter/master:v1 . docker push registry.gitlab.gnome.org/gnome/mutter/master:v1 Resolves: https://gitlab.gnome.org/GNOME/mutter/merge_requests/132
2018-06-14 15:01:35 -04:00
gitlab-ci.yml: Add check for issue or MR URL This adds a pipeline stage for merge requests that checks that the commit message contains an URL to either a issue or a merge request. This means that for merge requests without corresponding issues will always fail initially, as the merge request URL is not known until after it is created. This is still arguably better than accidentally merging merge requests without URLs. https://gitlab.gnome.org/GNOME/mutter/merge_requests/440
2019-02-05 12:19:43 -05:00
check-commit-log:
stage: review
ci: Ensure we clone a deep enough history for commit review It seems gitlab changed something recently in the default clone depth which made MRs with >10 commits to obscurely fail in the review stage. As per https://docs.gitlab.com/ee/ci/yaml/#shallow-cloning, bump it to 100 to allow bigger MRs. https://gitlab.gnome.org/GNOME/mutter/merge_requests/551
2019-04-24 06:24:12 -04:00
variables:
GIT_DEPTH: "100"
gitlab-ci.yml: Add check for issue or MR URL This adds a pipeline stage for merge requests that checks that the commit message contains an URL to either a issue or a merge request. This means that for merge requests without corresponding issues will always fail initially, as the merge request URL is not known until after it is created. This is still arguably better than accidentally merging merge requests without URLs. https://gitlab.gnome.org/GNOME/mutter/merge_requests/440
2019-02-05 12:19:43 -05:00
script:
- ./.gitlab-ci/check-commit-log.sh
only:
- merge_requests
Add .gitlab-ci.yml for build testing This adds compilation testing using meson on the gitlab instance. It uses a prebuild image built, described in .gitlab-ci/Dockerfile, based on Fedora 29. The image is build and published by running: cd .gitlab-ci/ docker build -t registry.gitlab.gnome.org/gnome/mutter/master:v1 . docker push registry.gitlab.gnome.org/gnome/mutter/master:v1 Resolves: https://gitlab.gnome.org/GNOME/mutter/merge_requests/132
2018-06-14 15:01:35 -04:00
build-mutter:
stage: build
script:
ci: Install to Mutter and GNOME Shell to /usr So GNOME Shell can find the pkg-config files properly. https://gitlab.gnome.org/GNOME/mutter/merge_requests/548
2019-04-23 11:33:43 -04:00
- meson . build -Dbuildtype=debugoptimized -Degl_device=true -Dwayland_eglstream=true --werror --prefix /usr
Add .gitlab-ci.yml for build testing This adds compilation testing using meson on the gitlab instance. It uses a prebuild image built, described in .gitlab-ci/Dockerfile, based on Fedora 29. The image is build and published by running: cd .gitlab-ci/ docker build -t registry.gitlab.gnome.org/gnome/mutter/master:v1 . docker push registry.gitlab.gnome.org/gnome/mutter/master:v1 Resolves: https://gitlab.gnome.org/GNOME/mutter/merge_requests/132
2018-06-14 15:01:35 -04:00
- ninja -C build
- ninja -C build install
gitlab-ci: Use artifacts to keep built data and reuse in test Make test to be dependent on build phase, saving artifacts for some time in order to just run the tests without performing any rebuild. https://gitlab.gnome.org/GNOME/mutter/merge_requests/408
2019-01-23 07:28:38 -05:00
artifacts:
ci: Test building without native backend support Nobody from the core team tests that configuration, so some non-guarded includes regularly sneak in. Avoid those build breakages by adding a corresponding job to the CI pipeline. https://gitlab.gnome.org/GNOME/mutter/merge_requests/637
2019-06-22 10:55:08 -04:00
expire_in: 1 day
paths:
- build
only:
- merge_requests
- /^.*$/
ci: Add a new 'build-without-opengl-and-glx' step To make sure we don't regress with this specific set of flags. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1151
2020-03-26 17:23:26 -04:00
build-without-opengl-and-glx:
stage: build
script:
- meson . build -Dbuildtype=debugoptimized -Dopengl=false -Dglx=false -Degl_device=true -Dwayland_eglstream=true --werror --prefix /usr
- ninja -C build
- ninja -C build install
artifacts:
expire_in: 1 day
paths:
- build
only:
- merge_requests
- /^.*$/
ci: Change the without-native-backend to not build with Wayland too There are two common ways of building mutter: With both the native backend and Wayland support (most common, used by most Linux distributions), and without the native backend and Wayland support (as is done by some BSD*s). To catch compilation errors in both these common build configurations, change the no-native-backend build phase to also not build with Wayland support. This also disables building mutter tests, as tests depend on Wayland to run. https://gitlab.gnome.org/GNOME/mutter/merge_requests/837
2019-10-09 04:42:35 -04:00
build-without-native-backend-and-wayland:
ci: Test building without native backend support Nobody from the core team tests that configuration, so some non-guarded includes regularly sneak in. Avoid those build breakages by adding a corresponding job to the CI pipeline. https://gitlab.gnome.org/GNOME/mutter/merge_requests/637
2019-06-22 10:55:08 -04:00
stage: build
script:
ci: Change the without-native-backend to not build with Wayland too There are two common ways of building mutter: With both the native backend and Wayland support (most common, used by most Linux distributions), and without the native backend and Wayland support (as is done by some BSD*s). To catch compilation errors in both these common build configurations, change the no-native-backend build phase to also not build with Wayland support. This also disables building mutter tests, as tests depend on Wayland to run. https://gitlab.gnome.org/GNOME/mutter/merge_requests/837
2019-10-09 04:42:35 -04:00
- meson . build -Dbuildtype=debugoptimized -Dnative_backend=false -Dudev=false -Dwayland=false -Dcore_tests=false --werror --prefix /usr
ci: Test building without native backend support Nobody from the core team tests that configuration, so some non-guarded includes regularly sneak in. Avoid those build breakages by adding a corresponding job to the CI pipeline. https://gitlab.gnome.org/GNOME/mutter/merge_requests/637
2019-06-22 10:55:08 -04:00
- ninja -C build
- ninja -C build install
artifacts:
gitlab-ci: Use artifacts to keep built data and reuse in test Make test to be dependent on build phase, saving artifacts for some time in order to just run the tests without performing any rebuild. https://gitlab.gnome.org/GNOME/mutter/merge_requests/408
2019-01-23 07:28:38 -05:00
expire_in: 1 day
paths:
- build
gitlab-ci.yml: Add check for issue or MR URL This adds a pipeline stage for merge requests that checks that the commit message contains an URL to either a issue or a merge request. This means that for merge requests without corresponding issues will always fail initially, as the merge request URL is not known until after it is created. This is still arguably better than accidentally merging merge requests without URLs. https://gitlab.gnome.org/GNOME/mutter/merge_requests/440
2019-02-05 12:19:43 -05:00
only:
- merge_requests
- /^.*$/
gitlab-ci: Add test stage The test stage runs the whole meson test suite inside Xvfb inside a dbus session. Running inside Xvfb is required as the cogl, clutter and mutter tests require to run on top of X11; the dbus session is required to make mutter succeed in owning names on the bus. This also updates the Dockerfile to include packages needed for running tests. https://gitlab.gnome.org/GNOME/mutter/issues/193
2018-08-17 08:15:29 -04:00
test-mutter:
stage: test
gitlab-ci: Use artifacts to keep built data and reuse in test Make test to be dependent on build phase, saving artifacts for some time in order to just run the tests without performing any rebuild. https://gitlab.gnome.org/GNOME/mutter/merge_requests/408
2019-01-23 07:28:38 -05:00
dependencies:
- build-mutter
gitlab-ci: Define exported global variables once Don't redefine XDG runtime and gsettings schema paths multiple times, just export the variables once and reuse them. https://gitlab.gnome.org/GNOME/mutter/merge_requests/408
2019-01-23 18:24:32 -05:00
variables:
XDG_RUNTIME_DIR: "$CI_PROJECT_DIR/runtime-dir"
GSETTINGS_SCHEMA_DIR: "$CI_PROJECT_DIR/build/data"
gitlab-ci: Use G_SLICE=always-malloc in tests This allows to catch errors better, as per MALLOC_CHECK_'s definition https://gitlab.gnome.org/GNOME/mutter/merge_requests/581
2019-05-16 18:06:04 -04:00
G_SLICE: "always-malloc"
gitlab-ci: Use MALLOC_CHECK_ and MALLOC_PERTURB_ env variables in tests Linux glibc supports a malloc implementation that is allows to be tunable using environment variables, to check allocation issues. When MALLOC_CHECK_ is set to 3, a diagnostic message is printed on stderr and the program is aborted. Setting the MALLOC_PERTURB_ environment variable causes the malloc functions in to return memory which has been wiped and initialized with the byte value of the environment variable. So use this features when running tests in order to catch better memory errors. https://gitlab.gnome.org/GNOME/mutter/merge_requests/578
2019-05-15 19:41:17 -04:00
MALLOC_CHECK_: "3"
ci: Disable a11y bus for tests While the regular session bus is provided by `dbus-run-session`, the a11y bus is spawn by the "normal" D-Bus daemon (that is, dbus-broker in F30). This currently fails, either due to a bug or some missing dependencies in the container environment. But as we don't actually need the additional bus, just disable it via the environment to make not break tests when updating the base image to F30. https://gitlab.gnome.org/GNOME/mutter/merge_requests/582
2019-05-20 12:40:34 -04:00
NO_AT_BRIDGE: "1"
ci: Make MALLOC_PERTURB_ less random The point is to not initialize to some non-zero value to find places incorrectly relying on blocks being zero initialized. Thus, there is no reason to have a different random number each time, and by having it the same, we have slightly more reproducable triggers, would we ever trigger anything due to this. https://gitlab.gnome.org/GNOME/mutter/merge_requests/591
2019-05-24 03:18:34 -04:00
MALLOC_PERTURB_: "123"
gitlab-ci: Add test stage The test stage runs the whole meson test suite inside Xvfb inside a dbus session. Running inside Xvfb is required as the cogl, clutter and mutter tests require to run on top of X11; the dbus session is required to make mutter succeed in owning names on the bus. This also updates the Dockerfile to include packages needed for running tests. https://gitlab.gnome.org/GNOME/mutter/issues/193
2018-08-17 08:15:29 -04:00
script:
ci: Run dconf update before running tests Otherwise tests will fail due to the following warning: (mutter-test-runner:3700): dconf-WARNING **: 06:39:42.124: unable to open file '/etc/dconf/db/local': Failed to open file “/etc/dconf/db/local”: open() failed: No such file or directory; expect degraded performance https://gitlab.gnome.org/GNOME/mutter/merge_requests/591
2019-05-24 02:48:23 -04:00
- dconf update
gitlab-ci: Define exported global variables once Don't redefine XDG runtime and gsettings schema paths multiple times, just export the variables once and reuse them. https://gitlab.gnome.org/GNOME/mutter/merge_requests/408
2019-01-23 18:24:32 -05:00
- mkdir -m 700 $XDG_RUNTIME_DIR
- glib-compile-schemas $GSETTINGS_SCHEMA_DIR
gitlab-ci: Use artifacts to keep built data and reuse in test Make test to be dependent on build phase, saving artifacts for some time in order to just run the tests without performing any rebuild. https://gitlab.gnome.org/GNOME/mutter/merge_requests/408
2019-01-23 07:28:38 -05:00
- >
dbus-run-session -- xvfb-run -s '+iglx -noreset'
gitlab-ci: Print error logs on failures https://gitlab.gnome.org/GNOME/mutter/merge_requests/581
2019-05-16 18:06:47 -04:00
meson test -C build --no-rebuild -t 10 --verbose --no-stdsplit --print-errorlogs --wrap catchsegv
gitlab-ci.yml: Add check for issue or MR URL This adds a pipeline stage for merge requests that checks that the commit message contains an URL to either a issue or a merge request. This means that for merge requests without corresponding issues will always fail initially, as the merge request URL is not known until after it is created. This is still arguably better than accidentally merging merge requests without URLs. https://gitlab.gnome.org/GNOME/mutter/merge_requests/440
2019-02-05 12:19:43 -05:00
only:
- merge_requests
- /^.*$/
ci: Build GNOME Shell at the test stage Hopefully this will allow us prevent merging branches that accidentally break GNOME Shell. https://gitlab.gnome.org/GNOME/mutter/merge_requests/548
2019-04-22 13:54:11 -04:00
can-build-gnome-shell:
stage: test
dependencies:
- build-mutter
before_script:
- meson install --no-rebuild -C build
script:
- .gitlab-ci/checkout-gnome-shell.sh
ci: Don't build gnome-shell's man pages One of the man pages is now generated using asciidoc, which is missing from the CI image. But given that this doesn't depend on mutter in any way, just disable man pages in the gnome-shell build instead of updating the Dockerfile. https://gitlab.gnome.org/GNOME/mutter/merge_requests/740
2019-08-21 16:30:41 -04:00
- meson gnome-shell gnome-shell/build --prefix /usr -Dman=false
ci: Build GNOME Shell at the test stage Hopefully this will allow us prevent merging branches that accidentally break GNOME Shell. https://gitlab.gnome.org/GNOME/mutter/merge_requests/548
2019-04-22 13:54:11 -04:00
- ninja -C gnome-shell/build install
only:
- merge_requests
- /^.*$/
Reference in New Issue Copy Permalink