AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-11-14 12:41:07 +00:00
Code Issues Projects Releases Wiki Activity
5942252175
gtk/.gitlab-ci.yml

486 lines
14 KiB
YAML
Raw Normal View History

ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
include:
- project: 'gnome/citemplates'
file: 'flatpak/flatpak_ci_initiative.yml'
Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
stages:
ci: Move style check to its own stage Drop the `.pre` phase.
2022-09-09 22:39:20 +00:00
- check
Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
- build
ci: Add a static analysis job Use the Clang static analysis tool. For the time being, we're going to allow it to fail, but the plan is to fix every issue it raises.
2020-02-25 19:06:39 +00:00
- analysis
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
- docs
ci: Deploy the API ref before flatpak
2020-02-12 18:10:49 +00:00
- flatpak
ci: Trigger a pages build Do not publish the API reference directly, but trigger a CI pipeline for the docs-gtk-org branch, which will then do the publishing.
2021-07-31 16:08:56 +00:00
- publish
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
- deploy
Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
gitlab-ci: Reenable ccache but disable it during the initial meson call There where some problems (??) with ccache not detecting changes during meson checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use the cache and pass things directly to the compiler.
2018-04-11 10:18:55 +00:00
.cache-paths: &cache-paths
paths:
- _ccache/
- subprojects/gdk-pixbuf/
- subprojects/glib/
- subprojects/graphene/
- subprojects/libepoxy/
- subprojects/pango/
ci: Refactor the CI pipeline We should have a single job for building both static and shared versions of GTK. On the other hand, having a separate job for the release build would be a plus. Additionally, we shouldn't use an opaque script to build GTK; the only step in the process that requires hand-holding is running the tests suites under Xvfb, and having the build options visible from the YAML file gives us a better idea of what kind of build we're running.
2020-01-29 09:35:10 +00:00
# Common variables
variables:
ci: Disable -Werror on all subprojects Would be nice if meson had a nicer way of doing this, but...
2021-11-04 00:41:05 +00:00
COMMON_MESON_FLAGS: "-Dwerror=true -Dcairo:werror=false -Dgi-docgen:werror=false -Dgraphene:werror=false -Dlibepoxy:werror=false -Dlibsass:werror=false -Dpango:werror=false -Dsassc:werror=false -Dgdk-pixbuf:werror=false -Dglib:werror=false -Dlibcloudproviders:werror=false -Dlibpng:werror=false -Dlibtiff:werror=false -Dsysprof:werror=false -Dwayland-protocols:werror=false -Dharfbuzz:werror=false -Dfreetype2:werror=false -Dfontconfig:werror=false -Dfribidi:werror=false -Dlibffi:werror=false -Dlibjpeg-turbo:werror=false -Dmutest:werror=false -Dpixman:werror=false -Dproxy-libintl:werror=false"
build: Start using meson feature options Use feature options for things that are optional features, update the docs. Visible changes here is that the 'print-backends' option got renamed to 'print' to go better with 'media', and the 'tracker3' option got renamed to 'tracker'. For options that have been changed into features, the syntax now is -Dfeature=enabled or -Dfeature=disabled or -Dfeature=auto.
2020-08-21 23:36:17 +00:00
BACKEND_FLAGS: "-Dx11-backend=true -Dwayland-backend=true -Dbroadway-backend=true"
ci: Add introspection to the feature flags It should be enabled by default, if we ever want to catch issues.
2023-05-21 11:22:50 +00:00
FEATURE_FLAGS: "-Dvulkan=enabled -Dcloudproviders=enabled -Dbuild-testsuite=true -Dintrospection=enabled"
ci: Increase the timeout multiplier We do have some slow tests.
2020-07-10 15:08:59 +00:00
MESON_TEST_TIMEOUT_MULTIPLIER: 3
CI: Reduce max number of tests to 8/4 CI is hitting various limits after we started out with 32. In particular, the default runners hit 90s test timeouts. And the asan runner runs into max threads limits, so reduce that one to 4 tests max.
2024-08-25 02:55:30 +00:00
MESON_TEST_MAX_PROCESSES: 8
ci: Fix a Vulkan problem in the F40 image Drop the powervr Vulkan driver, which otherwise interferes with proper functioning of our ci.
2024-08-08 18:18:41 +00:00
FEDORA_IMAGE: "registry.gitlab.gnome.org/gnome/gtk/fedora:v52"
ci: Refactor the CI pipeline We should have a single job for building both static and shared versions of GTK. On the other hand, having a separate job for the release build would be a plus. Additionally, we shouldn't use an opaque script to build GTK; the only step in the process that requires hand-holding is running the tests suites under Xvfb, and having the build options visible from the YAML file gives us a better idea of what kind of build we're running.
2020-01-29 09:35:10 +00:00
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
workflow:
rules:
Change workflow to enable MR pipelines This makes it possible to have macOS CI run for everything inside the main repository and for merge requests.
2023-08-11 18:52:07 +00:00
# run merge request pipelines
- if: $CI_PIPELINE_SOURCE == "merge_request_event"
# do not run branch pipelines if corresponding merge requests exist...
# (this avoids duplicate pipelines)
- if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
when: never
# ...but otherwise run branch pipelines
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
- if: $CI_COMMIT_BRANCH
Change workflow to enable MR pipelines This makes it possible to have macOS CI run for everything inside the main repository and for merge requests.
2023-08-11 18:52:07 +00:00
# run tag pipelines
- if: $CI_COMMIT_TAG
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
default:
ci: Add a simple auto-retry policy
2023-02-15 19:38:24 +00:00
retry:
max: 2
when:
- 'runner_system_failure'
- 'stuck_or_timeout_failure'
- 'scheduler_failure'
- 'api_failure'
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
interruptible: true
ci: Add a style check pass We should at least try to get the style check done by a machine, as opposed to have humans go through merge requests with coding style nitpicks.
2020-02-11 13:28:16 +00:00
style-check-diff:
ci: Move images into environment variables Currently we have to hunt all the `image` keys when updating the image in use for a job. We should centralise them all at the top of the file, so they are easy to update in one simple change.
2020-06-08 10:00:20 +00:00
image: $FEDORA_IMAGE
ci: Move style check to its own stage Drop the `.pre` phase.
2022-09-09 22:39:20 +00:00
stage: check
CI: Don't run style-check-diff by default We don't use it most of the time and it's also confusing to new contributors who think it's important to fix it. Keep it for manual runs, so that interested people can just click a button to see the results. It also makes it easy to turn back on later.
2023-02-14 23:53:02 +00:00
when: manual
ci: Add a style check pass We should at least try to get the style check done by a machine, as opposed to have humans go through merge requests with coding style nitpicks.
2020-02-11 13:28:16 +00:00
script:
- .gitlab-ci/run-style-check-diff.sh
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
.build-fedora-default:
ci: Move images into environment variables Currently we have to hunt all the `image` keys when updating the image in use for a job. We should centralise them all at the top of the file, so they are easy to update in one simple change.
2020-06-08 10:00:20 +00:00
image: $FEDORA_IMAGE
ci: Store the logs on build failure We should save the logs directory when the CI pipeline fails, so that we have a chance at debugging the failure.
2018-03-01 10:09:22 +00:00
artifacts:
ci: Add JUnit report for the test suite We can convert the JSON output for `meson test` into a JUnix XML report, which can be consumed by GitLab.
2019-04-05 17:23:13 +00:00
when: always
reports:
junit:
ci: Run tests with different backends Run the testsuite under x11, wayland and broadway in the fedora-x86_64 job. This requires us to use the v17 image which includes weston.
2020-05-15 13:44:24 +00:00
- "${CI_PROJECT_DIR}/_build/report-x11.xml"
- "${CI_PROJECT_DIR}/_build/report-wayland.xml"
ci: Pick up reports for all test setups We added a wayland_gl test setup recently, and all the setups have to be listed manually in .gitlab-ci.yml.
2023-11-25 14:20:16 +00:00
- "${CI_PROJECT_DIR}/_build/report-wayland_gl.xml"
ci: Run tests with different backends Run the testsuite under x11, wayland and broadway in the fedora-x86_64 job. This requires us to use the v17 image which includes weston.
2020-05-15 13:44:24 +00:00
- "${CI_PROJECT_DIR}/_build/report-broadway.xml"
ci: Store the logs on build failure We should save the logs directory when the CI pipeline fails, so that we have a chance at debugging the failure.
2018-03-01 10:09:22 +00:00
name: "gtk-${CI_COMMIT_REF_NAME}"
paths:
ci: Use the right path for the logs The meson-logs directory is under the `_build` directory.
2018-03-01 10:23:14 +00:00
- "${CI_PROJECT_DIR}/_build/meson-logs"
ci: Run tests with different backends Run the testsuite under x11, wayland and broadway in the fedora-x86_64 job. This requires us to use the v17 image which includes weston.
2020-05-15 13:44:24 +00:00
- "${CI_PROJECT_DIR}/_build/report*.xml"
- "${CI_PROJECT_DIR}/_build/report*.html"
- "${CI_PROJECT_DIR}/_build/testsuite/reftests/output/*/*.png"
CI: Include reftest nodes in artifacts
2022-05-18 17:13:39 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/reftests/output/*/*.node"
ci: Collect tools test output This should help understanding why some of them fail.
2021-07-28 17:41:33 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/tools/output/*/*"
ci: Run tests with different backends Run the testsuite under x11, wayland and broadway in the fedora-x86_64 job. This requires us to use the v17 image which includes weston.
2020-05-15 13:44:24 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/gsk/compare/*/*/*.png"
ci: Capture generated node files for gsk tests For some of the compare render variations (mask, clip, etc), it can be quite useful to have the generated node file around to reproduce the problem.
2024-02-12 00:02:39 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/gsk/compare/*/*/*.node"
ci: Run tests with different backends Run the testsuite under x11, wayland and broadway in the fedora-x86_64 job. This requires us to use the v17 image which includes weston.
2020-05-15 13:44:24 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/css/output/*/*.syscap"
ci: Improve headless test logging
2023-05-06 13:00:27 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/headless/*/*.log"
ci: Collect hello build logs
2021-06-09 11:35:25 +00:00
- "${CI_PROJECT_DIR}/_build_hello/meson-logs"
gitlab-ci: Reenable ccache but disable it during the initial meson call There where some problems (??) with ccache not detecting changes during meson checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use the cache and pass things directly to the compiler.
2018-04-11 10:18:55 +00:00
cache:
key: "$CI_JOB_NAME"
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
paths:
- _ccache/
fedora-x86_64:
extends: .build-fedora-default
stage: build
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
variables:
EXTRA_MESON_FLAGS: "--buildtype=debug --default-library=both"
script:
ci: Show OS release for our containers
2021-05-05 20:22:32 +00:00
- .gitlab-ci/show-info-linux.sh
ci: Redefine PATH
2022-12-14 18:35:52 +00:00
- export PATH="$HOME/.local/bin:$PATH"
ci: Download the subprojects Updating the subprojects will apparently fail if they haven't been downloaded.
2022-11-26 14:28:00 +00:00
- meson subprojects download
ci: Always update subprojects to latest revision Otherwise we're not actually updating anything. `meson subprojects download` will skip subprojects that already exist.
2022-12-19 03:38:28 +00:00
- meson subprojects update --reset
ci: Redefine PATH
2022-12-14 18:35:52 +00:00
- meson setup
${COMMON_MESON_FLAGS}
${EXTRA_MESON_FLAGS}
${BACKEND_FLAGS}
${FEATURE_FLAGS}
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
_build
ci: Test building against installed GTK This is meant to ensure that we e.g. install the right header files, and so on.
2021-06-08 21:39:34 +00:00
- meson compile -C _build
ci: Rebalance test runs Move x11 to the debug build, and make it a full run.
2023-11-25 16:03:15 +00:00
- .gitlab-ci/run-tests.sh _build x11 gtk
# only repeat test runs that are likely affected by test setups
ci: Run less tests Our test setups are mostly about varying the rendering environment (different backends, or renderers, etc). Therefore, we don't need to duplicate the runs of the css or node parser or path tests. Just run the gdk and gsk-gl tests under all setups.
2023-11-22 03:20:47 +00:00
- .gitlab-ci/run-tests.sh _build wayland_gl gtk:gdk,gtk:gsk-gl
ci: Add two flatpak jobs When building GTK through the CI infrastructure, it would help to have some ways of testing it; for instance, if we want to verify that theme changes are useful, or if we want to run the result without necessarily build it locally. This is where flatpak comes in handy. By having the CI build a flatpak buundle, and storing it as an artifact, of the GTK demos, we can easily point developers and designers to an installable binary that won't break their system, nor will require development tools and environments to run.
2018-03-20 16:08:45 +00:00
ci: Split the static and shared builds (again) Sadly, we can't do a static build with the profiling code enabled because we don't have a static GLib build available.
2020-01-29 10:31:47 +00:00
release-build:
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
extends: .build-fedora-default
ci: Refactor the CI pipeline We should have a single job for building both static and shared versions of GTK. On the other hand, having a separate job for the release build would be a plus. Additionally, we shouldn't use an opaque script to build GTK; the only step in the process that requires hand-holding is running the tests suites under Xvfb, and having the build options visible from the YAML file gives us a better idea of what kind of build we're running.
2020-01-29 09:35:10 +00:00
stage: build
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
Try building static libs on CI
2019-11-11 19:11:16 +00:00
variables:
ci: Refactor the CI pipeline We should have a single job for building both static and shared versions of GTK. On the other hand, having a separate job for the release build would be a plus. Additionally, we shouldn't use an opaque script to build GTK; the only step in the process that requires hand-holding is running the tests suites under Xvfb, and having the build options visible from the YAML file gives us a better idea of what kind of build we're running.
2020-01-29 09:35:10 +00:00
EXTRA_MESON_FLAGS: "--buildtype=release"
script:
ci: Show OS release for our containers
2021-05-05 20:22:32 +00:00
- .gitlab-ci/show-info-linux.sh
ci: Use catch to capture stacktraces For now, just try this out for the release build. If it works, we can add it to the other jobs too.
2024-07-02 02:07:41 +00:00
- mkdir _install
- export PATH="$HOME/.local/bin:${CI_PROJECT_DIR}/_install/bin:$PATH"
- .gitlab-ci/install-meson-project.sh --prefix ${CI_PROJECT_DIR}/_install https://gitlab.gnome.org/jadahl/catch.git main
ci: Download the subprojects Updating the subprojects will apparently fail if they haven't been downloaded.
2022-11-26 14:28:00 +00:00
- meson subprojects download
ci: Always update subprojects to latest revision Otherwise we're not actually updating anything. `meson subprojects download` will skip subprojects that already exist.
2022-12-19 03:38:28 +00:00
- meson subprojects update --reset
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
- meson setup
ci: Balance the work between jobs The fedora-x86-64 build does not only build with debug, it also does the hello build, and it runs the testsuite multiple times. Move the hello build to the fedora release build. The idea is that this lets us do more work in parallel, and spend less time waiting for the longest-running ci job.
2023-05-11 12:39:38 +00:00
--prefix=${CI_PROJECT_DIR}/_install
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
${COMMON_MESON_FLAGS}
${EXTRA_MESON_FLAGS}
${BACKEND_FLAGS}
${FEATURE_FLAGS}
_build
ci: Consistently use meson subcommands meson setup: configuration meson compile: compilation meson install installation Do not use ninja directly, and do not use `meson` as a synonym for `meson setup`.
2022-12-14 17:44:27 +00:00
- meson compile -C _build
ci: Balance the work between jobs The fedora-x86-64 build does not only build with debug, it also does the hello build, and it runs the testsuite multiple times. Move the hello build to the fedora release build. The idea is that this lets us do more work in parallel, and spend less time waiting for the longest-running ci job.
2023-05-11 12:39:38 +00:00
- meson install -C _build
- PKG_CONFIG_PATH=${CI_PROJECT_DIR}/_install/lib64/pkgconfig:${CI_PROJECT_DIR}/_install/share/pkgconfig meson setup _build_hello examples/hello
- LD_LIBRARY_PATH=${CI_PROJECT_DIR}/_install/lib64 meson compile -C _build_hello
ci: Run less tests Our test setups are mostly about varying the rendering environment (different backends, or renderers, etc). Therefore, we don't need to duplicate the runs of the css or node parser or path tests. Just run the gdk and gsk-gl tests under all setups.
2023-11-22 03:20:47 +00:00
- .gitlab-ci/run-tests.sh _build wayland gtk
Try building static libs on CI
2019-11-11 19:11:16 +00:00
ci: Add a clang build This is meant to catch build errors with clang.
2023-05-17 15:36:57 +00:00
fedora-clang:
extends: .build-fedora-default
stage: build
needs: []
variables:
EXTRA_MESON_FLAGS: "--buildtype=release"
script:
- .gitlab-ci/show-info-linux.sh
- export PATH="$HOME/.local/bin:$PATH"
- export CC=clang
- meson subprojects download
- meson subprojects update --reset
- meson setup
${COMMON_MESON_FLAGS}
${EXTRA_MESON_FLAGS}
${BACKEND_FLAGS}
${FEATURE_FLAGS}
_build
- meson compile -C _build
ci: add fedora-mingw64 job Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2022-01-06 12:01:40 +00:00
fedora-mingw64:
extends: .build-fedora-default
stage: build
needs: []
before_script:
- sudo dnf install -y
mingw64-filesystem
mingw64-gcc
mingw64-binutils
mingw64-cairo
mingw64-gdk-pixbuf
mingw64-gstreamer1-plugins-bad-free
mingw64-glib2
mingw64-libepoxy
mingw64-pango
# mingw64-graphene (rawhide)
script:
- .gitlab-ci/show-info-linux.sh
ci: Redefine PATH
2022-12-14 18:35:52 +00:00
- export PATH="$HOME/.local/bin:$PATH"
ci: Use newer meson
2023-05-04 00:01:20 +00:00
- pip3 install --user meson~=1.0
ci: Download the subprojects Updating the subprojects will apparently fail if they haven't been downloaded.
2022-11-26 14:28:00 +00:00
- meson subprojects download
ci: Always update subprojects to latest revision Otherwise we're not actually updating anything. `meson subprojects download` will skip subprojects that already exist.
2022-12-19 03:38:28 +00:00
- meson subprojects update --reset
ci: Remove the hack
2023-05-04 02:32:00 +00:00
- meson -Dintrospection=disabled -Dgraphene:introspection=disabled _build
- meson compile -C _build
ci: add fedora-mingw64 job Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
2022-01-06 12:01:40 +00:00
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
.mingw-defaults:
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
stage: build
tags:
CI: Switch to new Windows runners They use powershell instead of cmd.exe, use the tag win32-ps instead of win32, and run Windows 2016 instead of 2012r2. The old runners will be switched off in the comming weeks.
2020-04-29 17:36:40 +00:00
- win32-ps
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
script:
- C:\msys64\usr\bin\pacman --noconfirm -Syyuu
- C:\msys64\usr\bin\bash -lc "bash -x ./.gitlab-ci/test-msys2.sh"
gitlab-ci: Reenable ccache but disable it during the initial meson call There where some problems (??) with ccache not detecting changes during meson checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use the cache and pass things directly to the compiler.
2018-04-11 10:18:55 +00:00
cache:
CI: use bash style variable expansion for the mingw cache key It doesn't understand the powershell syntax which leads to the cache key being empty which leads to cache restore being skipped which leads to slow builds not using ccache. See https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2747
2020-05-06 19:19:52 +00:00
key: "$CI_JOB_NAME"
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
paths:
- _ccache/
- subprojects/gdk-pixbuf/
- subprojects/glib/
- subprojects/graphene/
- subprojects/libepoxy/
- subprojects/pango/
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
CI: Switch to 64bit mingw for the MSYS2 job 64 bit is more common now and also tests more things because sizeof(glong) != sizeof(gpointer)
2020-06-14 18:02:46 +00:00
msys2-mingw64:
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
extends: .mingw-defaults
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
variables:
CI: Switch to 64bit mingw for the MSYS2 job 64 bit is more common now and also tests more things because sizeof(glong) != sizeof(gpointer)
2020-06-14 18:02:46 +00:00
MSYSTEM: "MINGW64"
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
CHERE_INVOKING: "yes"
Provide GTK DLL as GitLab CI artifact
2022-01-19 11:17:28 +00:00
artifacts:
when: always
ci: Only use letters in "expose_as"
2022-01-19 15:39:44 +00:00
expose_as: 'Windows_DLL_MSYS2_64_bit_toolchain'
Provide GTK DLL as GitLab CI artifact
2022-01-19 11:17:28 +00:00
paths:
ci: Put gtk dll into an archive This avoids the wild card that makes the CI fail
2022-01-19 15:37:36 +00:00
- "${CI_PROJECT_DIR}/_build/gtkdll.tar.gz"
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
macos:
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
rules:
ci: Do not create macOS jobs for forks The runner is not available in forks (on purpose / for security reasons), so jobs created there will be stuck indefinitely until they timeout and fail the pipeline, which is undesireable. That also means that the initial goal to enable macOS jobs for all MRs is out of reach: if you are an external contributor (read: non-project member), your MR pipelines run in your fork, therefore have no access to the runner.
2023-08-25 23:56:59 +00:00
# Do not run in forks as the runner is not available there.
Allow macOS CI for runner's maintainer
2024-02-01 22:42:44 +00:00
# (except for dehesselle who maintains the runner)
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
- if: $CI_PROJECT_NAMESPACE != "GNOME" && $CI_PROJECT_NAMESPACE != "dehesselle"
when: never
- if: $RUNNER == "macosintel"
variables:
SDKROOT: /opt/sdks/MacOSX10.13.4.sdk
ci: Install ninja from wheel for Big Sur runner This avoids building it on the Big Sur Intel runner (because of Python 3.8) which would require us to provide cmake.
2024-03-10 16:12:16 +00:00
NINJA_PKG: $CI_API_V4_URL/projects/30745/packages/generic/ninja_macos/v1.11.1.1+9/ninja-1.11.1.1-cp38-cp38-macosx_11_0_x86_64.whl
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
when: manual
allow_failure: true
- if: $RUNNER == "macosarm"
variables:
SDKROOT: /opt/sdks/MacOSX11.3.sdk
ci: Install ninja from wheel for Big Sur runner This avoids building it on the Big Sur Intel runner (because of Python 3.8) which would require us to provide cmake.
2024-03-10 16:12:16 +00:00
NINJA_PKG: ninja==1.11.1.1
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
stage: build
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
parallel:
matrix:
- RUNNER: [ "macosintel", "macosarm" ]
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
tags:
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
- ${RUNNER}
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
needs: []
Re-enable macOS CI on new self-hosted runner
2023-07-19 11:51:50 +00:00
variables:
ci: Refactor job to use flags
2024-02-15 00:14:44 +00:00
EXTRA_MESON_FLAGS: ""
BACKEND_FLAGS: "-Dx11-backend=false -Dbroadway-backend=true"
FEATURE_FLAGS: "-Dmedia-gstreamer=disabled -Dintrospection=enabled -Dgobject-introspection:werror=false"
Re-enable macOS CI on new self-hosted runner
2023-07-19 11:51:50 +00:00
TMPDIR: /Users/Shared/work/tmp
PIP_CACHE_DIR: /Users/Shared/build/cache
PIPENV_CACHE_DIR: $PIP_CACHE_DIR
PYTHONPYCACHEPREFIX: $PIP_CACHE_DIR
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
before_script:
ci: Check for SDKROOT environment variable The SDKROOT variable is _the_ "master switch" to set the target OS version (much stricter compared to MACOSX_DEPLOYMENT_TARGET alone), yet it has no impact on the output of 'xcodebuild -showsdks'. Also rename the script to 'macos', it's not being called 'osx' anymore since 2016 (Sierra).
2024-02-18 19:31:36 +00:00
- .gitlab-ci/show-info-macos.sh
ci: Remove pygobject, pycairo and cmake They are not required anymore. Use the system's Python 3 as we no longer need to match the version with the externally provided wheels for pygobject and pycairo (courtesy of Inkscape's CI that also runs on that machine).
2024-02-18 19:09:20 +00:00
- python3 -m venv .venv
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
# Building the introspection feature requires pkg-config and bison.
ci: Use auditable sources for pkg-config and bison We need to provide pkg-config and bison to build the introspection feature. They were previously pre-installed on the runner and are now provided by dedicated projects for better reproducability to get away from "works on my machine".
2024-02-18 19:18:01 +00:00
- curl -L $CI_API_V4_URL/projects/30437/packages/generic/pkgconfig/v0.29.2+10/pkg-config-0.29.2+10_$(uname -m).tar.xz | tar -C .venv -xJ
- curl -L $CI_API_V4_URL/projects/30438/packages/generic/bison/v3.8.2+3/bison-3.8.2+3_$(uname -m).tar.xz | tar -C .venv -xJ
Re-enable macOS CI on new self-hosted runner
2023-07-19 11:51:50 +00:00
- source .venv/bin/activate
ci: Install ninja from wheel for Big Sur runner This avoids building it on the Big Sur Intel runner (because of Python 3.8) which would require us to provide cmake.
2024-03-10 16:12:16 +00:00
- pip3 install meson==1.3.2 $NINJA_PKG
ci: Add job for Apple Silicon This marks the beginning of transitioning to the arm64 architecture as the default. The x86_64 job remains present but is being phased out of 24/7 operations, i.e. the job is now on-demand only.
2024-02-18 19:24:58 +00:00
# We're not setting up ccache here on purpose as it accelerates the build
# so much that it triggers race conditions in the gobject-introspection
# subproject.
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
script:
Enable introspection in macOS CI This requires providing pkg-config and bison as well as pre-built wheels for Pycairo and PyGObject to make it work.
2023-08-24 14:44:34 +00:00
- meson setup
${COMMON_MESON_FLAGS}
${EXTRA_MESON_FLAGS}
ci: Refactor job to use flags
2024-02-15 00:14:44 +00:00
${BACKEND_FLAGS}
${FEATURE_FLAGS}
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
_build
ci: Consistently use meson subcommands meson setup: configuration meson compile: compilation meson install installation Do not use ninja directly, and do not use `meson` as a synonym for `meson setup`.
2022-12-14 17:44:27 +00:00
- meson compile -C _build
ci: Add a macos build Most of this is cribbed from glib. We don't use COMMON_MESON_FLAGS here, since disabling -Werror one subproject at a time is too painful for all the promoted sub-sub-projects. This needs a better solution in meson. Since this is a full rebuild of the entire stack, limit this to master and merge requests.
2021-01-03 03:34:52 +00:00
artifacts:
when: always
paths:
- "${CI_PROJECT_DIR}/_build/meson-logs"
ci: Add MSVC build This script is copied from glib CI.
2021-04-29 15:09:04 +00:00
vs2017-x64:
# TODO: Uncomment this when ready to merge.
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
# rules:
# - if: $CI_PROJECT_NAMESPACE == "GNOME"
ci: Add MSVC build This script is copied from glib CI.
2021-04-29 15:09:04 +00:00
stage: build
tags:
- win32-ps
needs: []
script:
- .gitlab-ci/test-msvc.bat
artifacts:
when: always
paths:
- "${CI_PROJECT_DIR}/_build/meson-logs"
ci: Use extends instead of YAML anchors The `extends` keyword is more readable than YAML's weird anchor syntax, and we don't have too many anchors in our job definitions anyway.
2020-05-15 12:21:45 +00:00
.flatpak-defaults:
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
image: "quay.io/gnome_infrastructure/gnome-runtime-images:gnome-master"
ci: Add two flatpak jobs When building GTK through the CI infrastructure, it would help to have some ways of testing it; for instance, if we want to verify that theme changes are useful, or if we want to run the result without necessarily build it locally. This is where flatpak comes in handy. By having the CI build a flatpak buundle, and storing it as an artifact, of the GTK demos, we can easily point developers and designers to an installable binary that won't break their system, nor will require development tools and environments to run.
2018-03-20 16:08:45 +00:00
stage: flatpak
ci: Allow flatpak jobs to fail We have more accurate CI jobs, now; the Flatpak jobs are nice to have.
2020-02-13 17:09:35 +00:00
allow_failure: true
ci: Update flatpak jobs The CI infrastructure was changed to run with fewer privileges, so we need to adapt our Flatpak jobs to compensate. See: https://mail.gnome.org/archives/desktop-devel-list/2020-February/msg00055.html
2020-02-19 15:04:58 +00:00
tags:
- flatpak
ci: Add two flatpak jobs When building GTK through the CI infrastructure, it would help to have some ways of testing it; for instance, if we want to verify that theme changes are useful, or if we want to run the result without necessarily build it locally. This is where flatpak comes in handy. By having the CI build a flatpak buundle, and storing it as an artifact, of the GTK demos, we can easily point developers and designers to an installable binary that won't break their system, nor will require development tools and environments to run.
2018-03-20 16:08:45 +00:00
artifacts:
paths:
ci: Use a common section for Flatpak jobs Avoid repeating blobs of YAML manually, and use the proper YAML mechanism to copy-paste blobs instead.
2018-04-11 16:45:29 +00:00
- "${APPID}-dev.flatpak"
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
- 'repo.tar'
ci: Add two flatpak jobs When building GTK through the CI infrastructure, it would help to have some ways of testing it; for instance, if we want to verify that theme changes are useful, or if we want to run the result without necessarily build it locally. This is where flatpak comes in handy. By having the CI build a flatpak buundle, and storing it as an artifact, of the GTK demos, we can easily point developers and designers to an installable binary that won't break their system, nor will require development tools and environments to run.
2018-03-20 16:08:45 +00:00
expire_in: 1 day
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
rules:
# Only build Flatpak bundles automatically on main
- if: $CI_COMMIT_BRANCH == "main"
- if: $CI_COMMIT_BRANCH != "main"
when: "manual"
ci: Use a common section for Flatpak jobs Avoid repeating blobs of YAML manually, and use the proper YAML mechanism to copy-paste blobs instead.
2018-04-11 16:45:29 +00:00
script:
- bash -x ./.gitlab-ci/flatpak-build.sh "${APPID}"
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
flatpak:demo:
extends: '.flatpak-defaults'
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Add manual jobs for Flatpak bundles Bundles can be useful on branches and MRs as an opt-in.
2019-04-05 18:15:11 +00:00
variables:
APPID: org.gtk.Demo4
ci: Add two flatpak jobs When building GTK through the CI infrastructure, it would help to have some ways of testing it; for instance, if we want to verify that theme changes are useful, or if we want to run the result without necessarily build it locally. This is where flatpak comes in handy. By having the CI build a flatpak buundle, and storing it as an artifact, of the GTK demos, we can easily point developers and designers to an installable binary that won't break their system, nor will require development tools and environments to run.
2018-03-20 16:08:45 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
flatpak:demo:aarch64:
extends: '.flatpak-defaults'
needs: []
tags:
- flatpak-aarch64
variables:
APPID: org.gtk.Demo4
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
flatpak:widget-factory:
extends: '.flatpak-defaults'
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Add manual jobs for Flatpak bundles Bundles can be useful on branches and MRs as an opt-in.
2019-04-05 18:15:11 +00:00
variables:
APPID: org.gtk.WidgetFactory4
gitlabci: Build and publish docs with gitlab pages.
2018-04-30 14:12:20 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
flatpak:widget-factory:aarch64:
extends: '.flatpak-defaults'
needs: []
tags:
- flatpak-aarch64
variables:
APPID: org.gtk.WidgetFactory4
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
flatpak:icon-browser:
extends: '.flatpak-defaults'
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Add manual jobs for Flatpak bundles Bundles can be useful on branches and MRs as an opt-in.
2019-04-05 18:15:11 +00:00
variables:
APPID: org.gtk.IconBrowser4
Add a flatpak manifest for org.gtk.IconBrowser4 And build it in ci.
2019-04-02 00:31:17 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
flatpak:icon-browser:aarch64:
extends: '.flatpak-defaults'
needs: []
tags:
- flatpak-aarch64
variables:
APPID: org.gtk.IconBrowser4
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
flatpak:node-editor:
extends: '.flatpak-defaults'
flatpak: add a NodeEditor demo
2022-07-25 12:38:55 +00:00
needs: []
variables:
APPID: org.gtk.gtk4.NodeEditor
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
flatpak:node-editor:aarch64:
extends: '.flatpak-defaults'
needs: []
tags:
- flatpak-aarch64
variables:
APPID: org.gtk.gtk4.NodeEditor
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
# Publish the demo apps to the GNOME Nightly repo
# https://wiki.gnome.org/Apps/Nightly
# https://gitlab.gnome.org/GNOME/Initiatives/-/wikis/DevOps-with-Flatpak
nightly demo:
extends: '.publish_nightly'
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
needs: ['flatpak:demo']
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
nightly demo aarch64:
extends: '.publish_nightly'
needs: ['flatpak:demo:aarch64']
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
nightly factory:
extends: '.publish_nightly'
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
needs: ['flatpak:widget-factory']
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
nightly factory aarch64:
extends: '.publish_nightly'
needs: ['flatpak:widget-factory:aarch64']
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
nightly icon-browser:
extends: '.publish_nightly'
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
needs: ['flatpak:icon-browser']
ci: publish demo apps to the Nightly repository
2020-11-13 18:00:17 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
nightly icon-browser aarch64:
extends: '.publish_nightly'
needs: ['flatpak:icon-browser:aarch64']
flatpak: add a NodeEditor demo
2022-07-25 12:38:55 +00:00
nightly node-editor:
extends: '.publish_nightly'
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
needs: ['flatpak:node-editor']
flatpak: add a NodeEditor demo
2022-07-25 12:38:55 +00:00
ci: Build and publish aarch64 flatpaks Close GNOME/gtk#5594
2023-02-15 19:18:56 +00:00
nightly node-editor aarch64:
extends: '.publish_nightly'
needs: ['flatpak:node-editor:aarch64']
ci: Add a static analysis job Use the Clang static analysis tool. For the time being, we're going to allow it to fail, but the plan is to fix every issue it raises.
2020-02-25 19:06:39 +00:00
static-scan:
ci: Move images into environment variables Currently we have to hunt all the `image` keys when updating the image in use for a job. We should centralise them all at the top of the file, so they are easy to update in one simple change.
2020-06-08 10:00:20 +00:00
image: $FEDORA_IMAGE
ci: Add a static analysis job Use the Clang static analysis tool. For the time being, we're going to allow it to fail, but the plan is to fix every issue it raises.
2020-02-25 19:06:39 +00:00
stage: analysis
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Add a static analysis job Use the Clang static analysis tool. For the time being, we're going to allow it to fail, but the plan is to fix every issue it raises.
2020-02-25 19:06:39 +00:00
variables:
EXTRA_MESON_FLAGS: "--buildtype=debug"
script:
ci: Redefine PATH
2022-12-14 18:35:52 +00:00
- export PATH="$HOME/.local/bin:$PATH"
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
- meson setup
${COMMON_MESON_FLAGS}
${EXTRA_MESON_FLAGS}
ci: Use the same options for the scan-build job In particular, not building the tests should help cutting down on time spent linking.
2023-05-11 14:16:34 +00:00
${BACKEND_FLAGS}
${FEATURE_FLAGS}
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
_scan_build
ci: Add a static analysis job Use the Clang static analysis tool. For the time being, we're going to allow it to fail, but the plan is to fix every issue it raises.
2020-02-25 19:06:39 +00:00
- ninja -C _scan_build scan-build
artifacts:
paths:
- _scan_build/meson-logs
allow_failure: true
ci: Disable f16c for asan It appears that f16c crashes asan instantly.
2022-12-20 05:29:48 +00:00
# Run tests with the address sanitizer. We need to turn off introspection
# and f16c, since they are incompatible with asan
ci: Add a build with asan Run our testsuite under asan. We do this in a separate build, since we need to turn off introspection to make the build succeed. As Michael Catanzaro pointed out, this requires a privileged runner in order to use kernel apis.
2020-07-09 02:22:31 +00:00
asan-build:
CI: Make asan a child of the default fedora build Effects of that: 1. Keep artifacts 2. Produce a test report 3. Caching for ccache
2024-08-21 19:35:05 +00:00
extends: .build-fedora-default
ci: Switch ASAN tests to runners tagged so
2020-07-20 14:41:46 +00:00
tags: [ asan ]
ci: Add a build with asan Run our testsuite under asan. We do this in a separate build, since we need to turn off introspection to make the build succeed. As Michael Catanzaro pointed out, this requires a privileged runner in order to use kernel apis.
2020-07-09 02:22:31 +00:00
stage: analysis
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Add a build with asan Run our testsuite under asan. We do this in a separate build, since we need to turn off introspection to make the build succeed. As Michael Catanzaro pointed out, this requires a privileged runner in order to use kernel apis.
2020-07-09 02:22:31 +00:00
variables:
CI: Reduce max number of tests to 8/4 CI is hitting various limits after we started out with 32. In particular, the default runners hit 90s test timeouts. And the asan runner runs into max threads limits, so reduce that one to 4 tests max.
2024-08-25 02:55:30 +00:00
MESON_TEST_MAX_PROCESSES: 4
ci: Add a build with asan Run our testsuite under asan. We do this in a separate build, since we need to turn off introspection to make the build succeed. As Michael Catanzaro pointed out, this requires a privileged runner in order to use kernel apis.
2020-07-09 02:22:31 +00:00
script:
ci: Redefine PATH
2022-12-14 18:35:52 +00:00
- export PATH="$HOME/.local/bin:$PATH"
ci: Build less for asan The asan build is all about running the tests with asan, so lets not waste time building demos and examples.
2023-06-06 02:05:16 +00:00
- CC=clang meson setup
--buildtype=debugoptimized
-Db_sanitize=address
-Db_lundef=false
-Dbuild-demos=false
-Dbuild-tests=false
-Dbuild-examples=false
-Dintrospection=disabled
-Df16c=disabled
_build
ci: Add a build with asan Run our testsuite under asan. We do this in a separate build, since we need to turn off introspection to make the build succeed. As Michael Catanzaro pointed out, this requires a privileged runner in order to use kernel apis.
2020-07-09 02:22:31 +00:00
- ninja -C _build
ci: Tweak the run-tests script The main change here is to pass the suites to run as an explicit argument. This is in preparation for running less tests.
2023-11-19 13:22:27 +00:00
- .gitlab-ci/run-tests.sh _build wayland gtk
ci: Add a build with asan Run our testsuite under asan. We do this in a separate build, since we need to turn off introspection to make the build succeed. As Michael Catanzaro pointed out, this requires a privileged runner in order to use kernel apis.
2020-07-09 02:22:31 +00:00
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
reference:
ci: Update the image v32 of the image includes wayland-protocols 1.21, and other updates from Fedora 34. While we are at it, drop gtk-doc from the image, and drop the separate DOCS_IMAGE - no longer used.
2021-06-09 11:10:13 +00:00
image: $FEDORA_IMAGE
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
stage: docs
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: []
ci: Deploy the API reference on our GitLab pages Now that we can build gtk-doc as a sub-project, we can go back to publishing the API reference for the master branch every time we build it.
2020-01-29 08:16:57 +00:00
script:
ci: Redefine PATH
2022-12-14 18:35:52 +00:00
- export PATH="$HOME/.local/bin:$PATH"
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
- meson setup
${COMMON_MESON_FLAGS}
--buildtype=release
--force-fallback-for=gdk-pixbuf,pango
-Dintrospection=enabled
build: Rename docs build options Rename gtk_doc to documentation and update_screenshots to screenshots. The old names are still accepted.
2023-08-05 00:05:07 +00:00
-Ddocumentation=true
ci: Build demos and man pages for docs That way, we should get all the man pages online.
2024-06-29 22:48:15 +00:00
-Dman-pages=true
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
-Dgdk-pixbuf:gtk_doc=true
ci: Use pangos documentation option The gtk_doc option has been deprecated in pango. Use the replacement to avoid a deprecation warning.
2024-04-21 13:39:40 +00:00
-Dpango:documentation=true
ci: Build demos and man pages for docs That way, we should get all the man pages online.
2024-06-29 22:48:15 +00:00
-Dbuild-demos=true
ci: Try to speed up builds a bit Don't build demos and tests, and only build the testsuite where we want to run it.
2023-01-13 12:26:41 +00:00
-Dbuild-examples=false
-Dbuild-tests=false
-Dbuild-testsuite=false
ci: Enable introspection for the docs build It is required, so lets not rely on defaults.
2023-01-02 16:24:05 +00:00
_build
ci: Update the reference job
2021-02-15 00:56:35 +00:00
- meson compile -C _build
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
- mkdir -p _reference/
ci: Update the reference job
2021-02-15 00:56:35 +00:00
- mv _build/docs/reference/gdk/gdk4/ _reference/gdk4/
- mv _build/docs/reference/gdk/gdk4-x11/ _reference/gdk4-x11/
- mv _build/docs/reference/gdk/gdk4-wayland/ _reference/gdk4-wayland/
- mv _build/docs/reference/gsk/gsk4/ _reference/gsk4/
- mv _build/docs/reference/gtk/gtk4/ _reference/gtk4/
docs: Install man pages as html This will let us link to them from the docs.
2024-05-29 22:47:37 +00:00
- mv _build/docs/reference/gtk/*.html _reference/gtk4/
ci: Build Pango and GdkPixbuf's docs We want to publish them alongside GTK's own API reference.
2021-03-23 12:25:08 +00:00
- mv _build/subprojects/pango/docs/Pango/ _reference/Pango/
- mv _build/subprojects/pango/docs/PangoCairo/ _reference/PangoCairo/
- mv _build/subprojects/pango/docs/PangoFc/ _reference/PangoFc/
- mv _build/subprojects/pango/docs/PangoFT2/ _reference/PangoFT2/
- mv _build/subprojects/pango/docs/PangoOT/ _reference/PangoOT/
- mv _build/subprojects/pango/docs/PangoXft/ _reference/PangoXft/
- mv _build/subprojects/gdk-pixbuf/docs/gdk-pixbuf/ _reference/gdk-pixbuf/
- mv _build/subprojects/gdk-pixbuf/docs/gdk-pixdata/ _reference/gdk-pixdata/
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
artifacts:
paths:
- _reference
ci: Trigger a pages build Do not publish the API reference directly, but trigger a CI pipeline for the docs-gtk-org branch, which will then do the publishing.
2021-07-31 16:08:56 +00:00
publish-docs:
ci: Force the fedora image for the publish-docs job Otherwise every CI runner might decide to use a different default image, and we'll end up on one that doesn't have curl.
2022-06-28 20:31:07 +00:00
image: fedora:latest
ci: Trigger a pages build Do not publish the API reference directly, but trigger a CI pipeline for the docs-gtk-org branch, which will then do the publishing.
2021-07-31 16:08:56 +00:00
stage: publish
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
interruptible: false
ci: Use DAG attributes Some jobs can run out of order, as they are entirely self-contained. If we use the newly added DAG attributes, we can speed up the CI pipeline.
2020-07-27 11:44:36 +00:00
needs: ['reference']
ci: Add a separate "docs" stage Don't build the API reference on deploy; build it in a separate job, instead, so we can run it on all pipelines, and deploy it only for master.
2020-02-25 16:42:07 +00:00
script:
ci: Trigger a pages build Do not publish the API reference directly, but trigger a CI pipeline for the docs-gtk-org branch, which will then do the publishing.
2021-07-31 16:08:56 +00:00
- "curl -X POST -F token=${PAGES_TRIGGER_TOKEN} -F ref=docs-gtk-org https://gitlab.gnome.org/api/v4/projects/665/trigger/pipeline"
ci: Switch from only/except to rules: keyword It's more flexible and allows us to combine the flatpak jobs
2023-02-15 19:10:40 +00:00
rules:
- if: $CI_COMMIT_REF_NAME == "main"
ci: Refactor job to use flags
2024-02-15 00:14:44 +00:00
Reference in New Issue Copy Permalink