nautilus/.gitlab-ci.yml

variables:
  GIT_SUBMODULE_STRATEGY: normal

stages:
- test
- cross_distro

.test_template: &distro_test
  script:
    - meson _build .
    - cd _build
    - ninja test

flatpak:master:
    image: registry.gitlab.com/alatiera/gnome-nightly-oci/gnome-master:latest
    stage: test
    script:
    - flatpak-builder --stop-at=nautilus app build-aux/flatpak/org.gnome.NautilusDevel.json
    # Make sure to keep this in sync with the Flatpak manifest, all arguments
    # are passed except the config-args because we build it ourselves
    - flatpak-builder --run app build-aux/flatpak/org.gnome.NautilusDevel.json meson --prefix=/app --libdir=/app/lib -Dprofile=development _build
    - flatpak-builder --run app build-aux/flatpak/org.gnome.NautilusDevel.json ninja -C _build install
    - flatpak-builder --finish-only --repo=repo app build-aux/flatpak/org.gnome.NautilusDevel.json
    # Make a Flatpak Nautilus bundle for people to test
    - flatpak build-bundle repo nautilus-dev.flatpak org.gnome.NautilusDevel
    # Run automatic tests inside the Flatpak env
    - flatpak-builder --run app build-aux/flatpak/org.gnome.NautilusDevel.json ninja -C _build test
    artifacts:
        paths:
        - nautilus-dev.flatpak
        - _build/meson-logs/meson-log.txt
        - _build/meson-logs/testlog.txt
        expire_in: 2 days
    cache:
        paths:
        - .flatpak-builder/cache

# Pick any distro to build the coverage
fedora:rawhide:
    image: fedora:rawhide
    stage: cross_distro
    script:
    - dnf install -y 'dnf-command(builddep)' redhat-rpm-config gcovr
    # Waiting for gcovr 3.5 to be released.
    - pip install git+https://github.com/gcovr/gcovr.git
    - dnf builddep -y nautilus
    - meson _build . -Db_coverage=true
    # Coverage data contains paths relative to the build directory,
    # so changing to it makes writing filter expressions easier.
    #
    # _build/src/ contains generated sources, so that is filtered out as well.
    - cd _build
    - ninja test
    - gcovr --root=.
        --exclude=src/
        --exclude=../data/
        --exclude=../eel/check-program.c
        --exclude=../eel/eel-debug.c
        --exclude=../eel/eel-lib-self-check-functions.c
        --exclude=../eel/eel-self-checks.c
        --exclude=../src/animation/
        --exclude=../src/gtk/
        --exclude=../src/nautilus-lib-self-check-functions.c
        --exclude=../src/nautilus-self-check-functions.c
        --exclude=../subprojects/libgd/
        --exclude=../test/
    coverage: '/^TOTAL.*\s+(\d+\%)$/'
    only:
    - schedules
    - web
    - tags

ubuntu:devel:
    image: ubuntu:devel
    stage: cross_distro
    before_script:
    # Ubuntu requires running update to fetch metadata and find packges
    - apt update
    - apt install -y gcc meson gettext itstool git libgtk-3-dev
                     libgnome-autoar-0-dev libgnome-desktop-3-dev
                     gobject-introspection libxml2-dev
                     libtracker-control-2.0-dev desktop-file-utils libgexiv2-dev
                     libgail-3-dev libtracker-sparql-2.0-dev
                     libgirepository1.0-dev
    <<: *distro_test
    only:
    - schedules
    - web
    - tags

opensuse:tumbleweed:
    image: opensuse:tumbleweed
    stage: cross_distro
    before_script:
    - zypper install -y gcc meson gettext-runtime gettext-tools itstool git
                        gtk3-devel gnome-autoar-devel libgnome-desktop-3-devel
                        gobject-introspection-devel libxml2-devel tracker-devel
                        desktop-file-utils libgexiv2-devel
    <<: *distro_test
    only:
    - schedules
    - web
    - tags
CI: let the GitLab runner fetch submodules 2018-03-18 13:40:35 +00:00			`variables:`
			`GIT_SUBMODULE_STRATEGY: normal`

CI: Fixed to previous commit and split build and test 2018-03-16 14:51:02 +00:00			`stages:`
CI: Create artifacts when test fail 2018-03-17 12:36:44 +00:00			`- test`
			`- cross_distro`
gitlabci: Use yaml anchors as templates. 2018-03-18 15:41:40 +00:00
			`.test_template: &distro_test`
			`script:`
			`- meson _build .`
			`- cd _build`
			`- ninja test`

CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00			`flatpak:master:`
flatpak: switch to using gnome-nightly 2018-03-19 07:51:30 +00:00			`image: registry.gitlab.com/alatiera/gnome-nightly-oci/gnome-master:latest`
CI: Create artifacts when test fail 2018-03-17 12:36:44 +00:00			`stage: test`
CI: Fixed to previous commit and split build and test 2018-03-16 14:51:02 +00:00			`script:`
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks. 2018-03-16 15:24:11 +00:00			`- flatpak-builder --stop-at=nautilus app build-aux/flatpak/org.gnome.NautilusDevel.json`
CI: Flapak: Add comment about keeping in sync with the manifest 2018-03-19 12:04:26 +00:00			`# Make sure to keep this in sync with the Flatpak manifest, all arguments`
			`# are passed except the config-args because we build it ourselves`
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks. 2018-03-16 15:24:11 +00:00			`- flatpak-builder --run app build-aux/flatpak/org.gnome.NautilusDevel.json meson --prefix=/app --libdir=/app/lib -Dprofile=development _build`
			`- flatpak-builder --run app build-aux/flatpak/org.gnome.NautilusDevel.json ninja -C _build install`
			`- flatpak-builder --finish-only --repo=repo app build-aux/flatpak/org.gnome.NautilusDevel.json`
CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00			`# Make a Flatpak Nautilus bundle for people to test`
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks. 2018-03-16 15:24:11 +00:00			`- flatpak build-bundle repo nautilus-dev.flatpak org.gnome.NautilusDevel`
CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00			`# Run automatic tests inside the Flatpak env`
general: Allow running in separate instance When hacking on Nautilus, it is very inconvenient to have to close any running instance before running the built version. This commit enables running three different instances by changing the application ID. Beside the default “profile” is one crafted for stable flatpak releases and one for development. The stable flatpak profile adds an identifying mark to the about dialog to aid collecting information in bug reports. The development profile is that plus additional styling to help visually identify the development instance. It also will be used when generating Flatpak bundles with the help of CI. Generally, the implementation is slightly hacky to allow all the different workflows, spanning from regular installations to GNOME Builder flatpak builds, as each comes with its own quirks. 2018-03-16 15:24:11 +00:00			`- flatpak-builder --run app build-aux/flatpak/org.gnome.NautilusDevel.json ninja -C _build test`
CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00			`artifacts:`
			`paths:`
gitlabci: Use single artifacts block. Workaround for https://gitlab.com/gitlab-org/gitlab-ce/issues/34954 2018-03-19 08:19:43 +00:00			`- nautilus-dev.flatpak`
CI: fix build log path As of d36fa3fdaba2c249cff8ff9b0861f100d8b920b8, the build directory is in the source checkout. 2018-03-18 17:10:20 +00:00			`- _build/meson-logs/meson-log.txt`
CI: Flatpak: Fix typo 2018-03-19 08:35:07 +00:00			`- _build/meson-logs/testlog.txt`
gitlabci: Use single artifacts block. Workaround for https://gitlab.com/gitlab-org/gitlab-ce/issues/34954 2018-03-19 08:19:43 +00:00			`expire_in: 2 days`
gitlabci: Add caching for the flatpak build. 2018-03-18 15:53:57 +00:00			`cache:`
			`paths:`
			`- .flatpak-builder/cache`

CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00			`# Pick any distro to build the coverage`
			`fedora:rawhide:`
			`image: fedora:rawhide`
			`stage: cross_distro`
			`script:`
			`- dnf install -y 'dnf-command(builddep)' redhat-rpm-config gcovr`
			`# Waiting for gcovr 3.5 to be released.`
			`- pip install git+https://github.com/gcovr/gcovr.git`
CI: No idea how, but I removed previous code. Readding. 2018-03-17 00:13:53 +00:00			`- dnf builddep -y nautilus`
CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00			`- meson _build . -Db_coverage=true`
CI: Avoid installing packages for Flatpak 2018-03-16 14:58:24 +00:00			`# Coverage data contains paths relative to the build directory,`
			`# so changing to it makes writing filter expressions easier.`
			`#`
			`# _build/src/ contains generated sources, so that is filtered out as well.`
CI: Fixed to previous commit and split build and test 2018-03-16 14:51:02 +00:00			`- cd _build`
			`- ninja test`
			`- gcovr --root=.`
			`--exclude=src/`
			`--exclude=../data/`
			`--exclude=../eel/check-program.c`
			`--exclude=../eel/eel-debug.c`
			`--exclude=../eel/eel-lib-self-check-functions.c`
			`--exclude=../eel/eel-self-checks.c`
			`--exclude=../src/animation/`
			`--exclude=../src/gtk/`
			`--exclude=../src/nautilus-lib-self-check-functions.c`
			`--exclude=../src/nautilus-self-check-functions.c`
			`--exclude=../subprojects/libgd/`
			`--exclude=../test/`
			`coverage: '/^TOTAL.*\s+(\d+\%)$/'`
CI: Add weekly builds in major dev distributions 2018-03-16 16:57:23 +00:00			`only:`
CI: Fix typo 2018-03-16 17:00:33 +00:00			`- schedules`
gitlabci: Allow for the cross-distro state to be triggered manually from the web gui. 2018-03-18 15:43:07 +00:00			`- web`
			`- tags`
CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00
CI: Create artifacts when test fail 2018-03-17 12:36:44 +00:00			`ubuntu:devel:`
CI: Add weekly builds in major dev distributions 2018-03-16 16:57:23 +00:00			`image: ubuntu:devel`
CI: Create artifacts when test fail 2018-03-17 12:36:44 +00:00			`stage: cross_distro`
gitlabci: Use yaml anchors as templates. 2018-03-18 15:41:40 +00:00			`before_script:`
CI: Ubuntu: Update before installing packages to fetch the metadata 2018-03-17 12:23:19 +00:00			`# Ubuntu requires running update to fetch metadata and find packges`
			`- apt update`
CI: Update Ubuntu packages 2018-03-17 09:22:12 +00:00			`- apt install -y gcc meson gettext itstool git libgtk-3-dev`
			`libgnome-autoar-0-dev libgnome-desktop-3-dev`
			`gobject-introspection libxml2-dev`
			`libtracker-control-2.0-dev desktop-file-utils libgexiv2-dev`
CI: Ubuntu: Add libgirreposiroty1.0-dev 2018-03-17 13:24:56 +00:00			`libgail-3-dev libtracker-sparql-2.0-dev`
			`libgirepository1.0-dev`
gitlabci: Use yaml anchors as templates. 2018-03-18 15:41:40 +00:00			`<<: *distro_test`
CI: Add weekly builds in major dev distributions 2018-03-16 16:57:23 +00:00			`only:`
CI: Fix typo 2018-03-16 17:00:33 +00:00			`- schedules`
gitlabci: Allow for the cross-distro state to be triggered manually from the web gui. 2018-03-18 15:43:07 +00:00			`- web`
			`- tags`
CI: Use only Flatpak build for MR's So everyone uses the same environment, including the CI. Distributions will be tested weekly. 2018-03-17 23:16:06 +00:00
CI: Create artifacts when test fail 2018-03-17 12:36:44 +00:00			`opensuse:tumbleweed:`
CI: Add weekly builds in major dev distributions 2018-03-16 16:57:23 +00:00			`image: opensuse:tumbleweed`
CI: Create artifacts when test fail 2018-03-17 12:36:44 +00:00			`stage: cross_distro`
gitlabci: Use yaml anchors as templates. 2018-03-18 15:41:40 +00:00			`before_script:`
CI: Seems gettext is not available? It works locally though :/ 2018-03-17 10:31:58 +00:00			`- zypper install -y gcc meson gettext-runtime gettext-tools itstool git`
			`gtk3-devel gnome-autoar-devel libgnome-desktop-3-devel`
CI: Update OpenSUSE 2018-03-16 23:18:01 +00:00			`gobject-introspection-devel libxml2-devel tracker-devel`
			`desktop-file-utils libgexiv2-devel`
gitlabci: Use yaml anchors as templates. 2018-03-18 15:41:40 +00:00			`<<: *distro_test`
CI: Add weekly builds in major dev distributions 2018-03-16 16:57:23 +00:00			`only:`
CI: build from pre-existing checkout This should make MRs work properly and fix any issues regarding running tests. 2018-03-18 11:06:57 +00:00			`- schedules`
gitlabci: Allow for the cross-distro state to be triggered manually from the web gui. 2018-03-18 15:43:07 +00:00			`- web`
			`- tags`