AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-12-28 14:31:10 +00:00
Code Issues Projects Releases Wiki Activity
a772bf7517
gtk/.gitlab-ci.yml

126 lines
2.8 KiB
YAML
Raw Normal View History

Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
stages:
- build
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
- flatpak
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
- 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/
Try building static libs on CI
2019-11-11 19:11:16 +00:00
fedora-x86_64: &fedora-x86_64-defaults
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
image: registry.gitlab.gnome.org/gnome/gtk/master:v10
Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
stage: build
script:
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
- bash -x ./.gitlab-ci/test-docker.sh
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_PROJECT_DIR}/_build/report.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: 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
- "${CI_PROJECT_DIR}/_build/report.xml"
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
- "${CI_PROJECT_DIR}/_build/report.html"
ci: Cache the reftest artifacts Keeping the reftest output images as artifacts of a job allows us to browse them and download them straight from GitLab.
2019-04-12 19:58:29 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/reftests/output/*.png"
Save gsk output from ci
2019-06-03 01:06:31 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/gsk/compare/*/*.png"
ci: Save syscap files from performance tests They might become useful at some point.
2020-01-22 20:55:31 +00:00
- "${CI_PROJECT_DIR}/_build/testsuite/css/output/*.syscap"
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"
<<: *cache-paths
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
Try building static libs on CI
2019-11-11 19:11:16 +00:00
fedora-x86_64-staticlibs:
variables:
EXTRA_MESON_FLAGS: "-Ddefault_library=both"
<<: *fedora-x86_64-defaults
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
.mingw-defaults: &mingw-defaults
stage: build
tags:
- win32
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:
key: "%CI_JOB_NAME%"
<<: *cache-paths
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +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
msys2-mingw32:
gitlab-ci: Add a 32bit mingw build
2018-04-06 16:15:38 +00:00
variables:
MSYSTEM: "MINGW32"
CHERE_INVOKING: "yes"
<<: *mingw-defaults
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
.flatpak-defaults: &flatpak-defaults
ci: Update the image for the Flatpak jobs The gnome-nightly-oci registry was moved to gitlab.gnome.org, so we need to change the image we use when building Flatpak bundles in our CI pipeline.
2018-07-04 17:32:59 +00:00
image: registry.gitlab.gnome.org/gnome/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
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: 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: 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: 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
# Manual jobs, for branches and MRs
.flatpak-manual: &flatpak-manual
<<: *flatpak-defaults
when: manual
# Only build Flatpak bundles automatically on master
.flatpak-master: &flatpak-master
<<: *flatpak-defaults
only:
- master
flatpak-manual:demo:
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
variables:
gtk-demo: Rename to org.gtk.Demo4
2019-04-01 22:49:09 +00:00
APPID: org.gtk.Demo4
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
<<: *flatpak-manual
flatpak-master:demo:
variables:
APPID: org.gtk.Demo4
<<: *flatpak-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
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
flatpak-manual:widget-factory:
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
variables:
widget-factory: Rename to org.gtk.WidgetFactory4
2019-04-01 23:58:30 +00:00
APPID: org.gtk.WidgetFactory4
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
<<: *flatpak-manual
flatpak-master:widget-factory:
variables:
APPID: org.gtk.WidgetFactory4
<<: *flatpak-master
gitlabci: Build and publish docs with gitlab pages.
2018-04-30 14:12:20 +00:00
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
flatpak-manual:icon-browser:
Add a flatpak manifest for org.gtk.IconBrowser4 And build it in ci.
2019-04-02 00:31:17 +00:00
variables:
APPID: org.gtk.IconBrowser4
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
<<: *flatpak-manual
flatpak-master:icon-browser:
variables:
APPID: org.gtk.IconBrowser4
<<: *flatpak-master
Add a flatpak manifest for org.gtk.IconBrowser4 And build it in ci.
2019-04-02 00:31:17 +00:00
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
pages:
image: registry.gitlab.gnome.org/gnome/gtk/master:v10
stage: deploy
script:
- meson -Dgtk_doc=true _build .
- ninja -C _build
- ninja -C _build gdk4-doc gsk4-doc gtk4-doc
- mkdir -p public/
- mv _build/docs/reference/gtk/html/ public/gtk/
- mv _build/docs/reference/gdk/html/ public/gdk/
- mv _build/docs/reference/gsk/html/ public/gsk/
artifacts:
paths:
- public
only:
- master
Reference in New Issue Copy Permalink