luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-14 05:16:18 +01:00
Code Issues Packages Projects Releases Wiki Activity
8f4155c124
glib/.gitlab-ci.yml

360 lines
10 KiB
YAML
Raw Normal View History

ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
stages:
ci: Run the style-check pipeline stage first Don’t waste CI resources on compiling things which don’t comply with the style rules. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-26 13:17:42 +01:00
- style-check
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
- build
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
- coverage
ci: Add scan-build job in a new ‘analysis’ pipeline stage Use Meson’s support for running scan-build (Clang’s static analyser) against the build, so that we get static analysis of each pipeline. Add it in a new pipeline stage, after code coverage, so that we don’t waste resources on it unless the unit tests pass — a static analysis build takes perhaps 10× as long as a normal GCC build. https://mesonbuild.com/howtox.html#use-clang-static-analyzer Currently, the static analysis results are uploaded as artifacts, but the job will always succeed (regardless of whether there are any bugs found in the analysis). Currently, a large number of reports are outputted by the analyser, which need to be fixed before we can gate the pipeline on it. Furthermore, in order to get scan-build to exit with a non-zero status if any bugs are found, we need to depend on Meson ≥ 0.49.0, which contains the fix https://github.com/mesonbuild/meson/issues/4334, allowing us to add the following to .gitlab-ci.yml: ``` variables: # Exit with a non-zero status if any bugs are found SCANBUILD: "scan-build --status-bugs" ``` Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-12-28 00:32:39 +01:00
- analysis
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
- deploy
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
cache:
paths:
- _ccache/
ci: unify the test timeout multiplier across jobs Introduce a MESON_TEST_TIMEOUT_MULTIPLIER env var and use it in all test scripts.
2018-05-26 20:17:15 +02:00
variables:
MESON_TEST_TIMEOUT_MULTIPLIER: 2
Fix failing tests when G_MESSAGES_DEBUG is set (again) Similar issue was fixed with commit f929d148, but it's happening again. Define G_MESSAGES_DEBUG=all when running CI to ensure we won't regress anymore.
2018-08-16 20:31:55 +02:00
G_MESSAGES_DEBUG: all
ci: Upgrade meson to 0.48.0 and use --fatal-meson-warnings
2018-09-24 16:19:18 +02:00
MESON_COMMON_OPTIONS: "--buildtype debug --fatal-meson-warnings"
ci: unify the test timeout multiplier across jobs Introduce a MESON_TEST_TIMEOUT_MULTIPLIER env var and use it in all test scripts.
2018-05-26 20:17:15 +02:00
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
.only-default:
ci: Factor out only/except properties from jobs We can use a template to factor these out and make things a bit more maintainable. This should introduce no functional changes. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 12:06:32 +01:00
only:
- branches
except:
- tags
CI: Code check formating in CI
2019-11-11 21:21:25 +01:00
style-check-diff:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
CI: Code check formating in CI
2019-11-11 21:21:25 +01:00
image: registry.gitlab.gnome.org/gnome/glib/debian-stable:v5
stage: style-check
allow_failure: true
script:
ci: Move style-check-diff commands out to a separate sh file This doesn’t change how they run, but does split the code out a bit and mean we can interleave it with comments. Should make it a little less vile. Suggested by Emmanuele Bassi; see !1252. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:44:24 +01:00
- .gitlab-ci/run-style-check-diff.sh
CI: Code check formating in CI
2019-11-11 21:21:25 +01:00
ci: Use shorter job names Job names in gitlab pipeline view gets truncated to "fedora-meson-..." for all jobs which is not really useful. All our CIs are using Meson, and the host distro is not relevant when doing cross builds.
2018-06-22 17:08:06 +02:00
fedora-x86_64:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Use new Fedora v5 Docker image for all CI jobs v5 was built using the fedora.Dockerfile updates from the previous few commits. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 14:22:26 +01:00
image: registry.gitlab.gnome.org/gnome/glib/fedora:v5
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
stage: build
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
variables:
ci: No need to "cd _build" and set prefix/libdir
2018-06-05 19:58:48 +02:00
CFLAGS: "-coverage -ftest-coverage -fprofile-arcs"
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
script:
CI: Test static build on installed glib
2018-09-26 16:56:10 +02:00
- meson ${MESON_COMMON_OPTIONS}
--werror
--default-library=both
--prefix=$HOME/glib-installed
--libdir=lib
-Dsystemtap=true
-Ddtrace=true
-Dfam=true
-Dinstalled_tests=true
_build
ci: No need to "cd _build" and set prefix/libdir
2018-06-05 19:58:48 +02:00
- ninja -C _build
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
- mkdir -p _coverage
ci: Add lcov configuration to ignore g_return_*if_fail()/g_assert*() While we can’t add markers to the macro implementations to cause lcov to ignore them automatically, we can change our lcov configuration to ignore all calls to them. See https://github.com/linux-test-project/lcov/issues/44. This causes all the un-takeable branches and un-reachable assertions to be ignored by our code coverage, which bumps our statistics: • Lines: 74.9% → 74.8% • Functions: 82.3% → 82.3% • Branches: 53.3% → 64.2% The rationale is that nobody should be testing programmer error handling, as g_return_*if_fail() are used to guard against — so it’s not reasonable to count missed branches like that in code coverage statistics. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-10-03 15:47:26 +02:00
- lcov --config-file .gitlab-ci/lcovrc --directory _build --capture --initial --output-file "_coverage/${CI_JOB_NAME}-baseline.lcov"
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
- .gitlab-ci/run-tests.sh
ci: Add lcov configuration to ignore g_return_*if_fail()/g_assert*() While we can’t add markers to the macro implementations to cause lcov to ignore them automatically, we can change our lcov configuration to ignore all calls to them. See https://github.com/linux-test-project/lcov/issues/44. This causes all the un-takeable branches and un-reachable assertions to be ignored by our code coverage, which bumps our statistics: • Lines: 74.9% → 74.8% • Functions: 82.3% → 82.3% • Branches: 53.3% → 64.2% The rationale is that nobody should be testing programmer error handling, as g_return_*if_fail() are used to guard against — so it’s not reasonable to count missed branches like that in code coverage statistics. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-10-03 15:47:26 +02:00
- lcov --config-file .gitlab-ci/lcovrc --directory _build --capture --output-file "_coverage/${CI_JOB_NAME}.lcov"
CI: Test static build on installed glib
2018-09-26 16:56:10 +02:00
# FIXME: We should run all installed tests, but do only this one for now
# because it cannot run uninstalled. Reconfigure with dtrace disabled
# because it breaks static link.
- meson configure -Ddtrace=false _build
- ninja -C _build install
- GLIB_TEST_COMPILATION=1 $HOME/glib-installed/libexec/installed-tests/glib/static-link.py $HOME/glib-installed/lib/pkgconfig
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
artifacts:
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
reports:
junit: "_build/${CI_JOB_NAME}-report.xml"
ci: Clarify artifact naming Put the job name and commit identifier in the artifact names. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-29 11:54:29 +02:00
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
ci: Always export artifacts from Fedora build The default `when: on_success` means no artifacts are exported when the tests fail, which is precisely when we want to see the artifacts. Always export them, and rely on GitLab to garbage collect them as appropriate (typically after 30 days, I think). Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-29 11:53:41 +02:00
when: always
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
paths:
ci: Include config.h and glibconfig.h in CI output artifacts It’s useful to see what configuration was generated. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-08-29 12:16:58 +02:00
- "_build/config.h"
- "_build/glib/glibconfig.h"
ci: Be consistent on artifact naming
2018-06-05 20:01:53 +02:00
- "_build/meson-logs"
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
- "_build/${CI_JOB_NAME}-report.xml"
ci: Be consistent on artifact naming
2018-06-05 20:01:53 +02:00
- "_coverage"
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
ci: Add a debian-stable job So we can test ancient toolchains.
2019-04-30 15:01:56 +02:00
debian-stable-x86_64:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Update all Debian CI runners to use v5 of the Dockerfile This shouldn’t affect them (since it just adds the `clang-format-7` package), but it’s good to keep everything on the same version. Signed-off-by: Philip Withnall <withnall@endlessm.com> See: #1552
2019-11-25 11:51:14 +01:00
image: registry.gitlab.gnome.org/gnome/glib/debian-stable:v5
ci: Add a debian-stable job So we can test ancient toolchains.
2019-04-30 15:01:56 +02:00
stage: build
script:
- meson ${MESON_COMMON_OPTIONS}
--werror
--default-library=both
--prefix=$HOME/glib-installed
--libdir=lib
-Dsystemtap=true
-Ddtrace=true
-Dfam=true
-Dinstalled_tests=true
_build
- ninja -C _build
- .gitlab-ci/run-tests.sh
artifacts:
reports:
junit: "_build/${CI_JOB_NAME}-report.xml"
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
paths:
- "_build/config.h"
- "_build/glib/glibconfig.h"
- "_build/meson-logs"
- "_build/${CI_JOB_NAME}-report.xml"
ci: Add a build with G_DISABLE_ASSERT defined We want GLib to build correctly with this defined, and for all its tests to still pass. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1708
2019-03-05 12:02:24 +01:00
G_DISABLE_ASSERT:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Use new Fedora v5 Docker image for all CI jobs v5 was built using the fedora.Dockerfile updates from the previous few commits. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 14:22:26 +01:00
image: registry.gitlab.gnome.org/gnome/glib/fedora:v5
ci: Add a build with G_DISABLE_ASSERT defined We want GLib to build correctly with this defined, and for all its tests to still pass. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1708
2019-03-05 12:02:24 +01:00
stage: build
variables:
CPPFLAGS: "-DG_DISABLE_ASSERT"
script:
- meson ${MESON_COMMON_OPTIONS}
--werror
-Dsystemtap=true
-Ddtrace=true
-Dfam=true
-Dinstalled_tests=true
_build
- ninja -C _build
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
- bash -x ./.gitlab-ci/run-tests.sh
ci: Add a build with G_DISABLE_ASSERT defined We want GLib to build correctly with this defined, and for all its tests to still pass. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1708
2019-03-05 12:02:24 +01:00
artifacts:
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
reports:
junit: "_build/${CI_JOB_NAME}-report.xml"
ci: Add a build with G_DISABLE_ASSERT defined We want GLib to build correctly with this defined, and for all its tests to still pass. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1708
2019-03-05 12:02:24 +01:00
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
paths:
- "_build/config.h"
- "_build/glib/glibconfig.h"
- "_build/meson-logs"
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
- "_build/${CI_JOB_NAME}-report.xml"
ci: Add a build with G_DISABLE_ASSERT defined We want GLib to build correctly with this defined, and for all its tests to still pass. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1708
2019-03-05 12:02:24 +01:00
ci: Add valgrind memcheck support on Fedora Add a separate CI job which runs memcheck on the unit tests. This is done as a separate job from the main build, since we don’t want it to interact with code coverage at all. Currently, failure of this job is ignored. Issue #333 will eventually fix that. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #487
2018-06-26 18:23:09 +02:00
valgrind:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Use new Fedora v5 Docker image for all CI jobs v5 was built using the fedora.Dockerfile updates from the previous few commits. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 14:22:26 +01:00
image: registry.gitlab.gnome.org/gnome/glib/fedora:v5
ci: Add valgrind memcheck support on Fedora Add a separate CI job which runs memcheck on the unit tests. This is done as a separate job from the main build, since we don’t want it to interact with code coverage at all. Currently, failure of this job is ignored. Issue #333 will eventually fix that. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #487
2018-06-26 18:23:09 +02:00
stage: analysis
variables:
MESON_TEST_TIMEOUT_MULTIPLIER: 10
script:
- meson ${MESON_COMMON_OPTIONS}
--werror
-Dsystemtap=true
-Ddtrace=true
-Dfam=true
-Dinstalled_tests=true
_build
- ninja -C _build
- bash -x ./.gitlab-ci/run-tests.sh
--log-file _build/meson-logs/testlog-valgrind.json
--wrap "valgrind --tool=memcheck --error-exitcode=1 --track-origins=yes --leak-check=full --leak-resolution=high --num-callers=50 --show-leak-kinds=definite,possible --show-error-list=yes --suppressions=${CI_PROJECT_DIR}/glib.supp"
--no-suite no-valgrind
--no-suite slow
# FIXME: Remove this when we have zero valgrind leaks.
# https://gitlab.gnome.org/GNOME/glib/issues/333
allow_failure: true
artifacts:
reports:
junit: "_build/${CI_JOB_NAME}-report.xml"
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
paths:
- "_build/config.h"
- "_build/glib/glibconfig.h"
- "_build/meson-logs"
ci: factor out cross compilation jobs definitions
2018-06-27 15:14:38 +02:00
.cross-template: &cross-template
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
Add Android CI This adds to the CI a cross build for Android NDK r16 API 21 (because thats what GStreamer currently use) for arm64. GNU iconv must be built manually into our docker image because Android NDK doesn't seems to ship it. The latest NDK r17 API 28 has iconv.h but iconv_open() symbol isn't found by the linker. Looks like broken NDK. libffi also needs to be built manually because the meson subproject doesn't support building for Android platform. It needs a recent RC release because latest stable release is 4 years old and fails to build. Fixes #1385.
2018-05-20 06:14:56 +02:00
stage: build
artifacts:
ci: Be consistent on artifact naming
2018-06-05 20:01:53 +02:00
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
Add Android CI This adds to the CI a cross build for Android NDK r16 API 21 (because thats what GStreamer currently use) for arm64. GNU iconv must be built manually into our docker image because Android NDK doesn't seems to ship it. The latest NDK r17 API 28 has iconv.h but iconv_open() symbol isn't found by the linker. Looks like broken NDK. libffi also needs to be built manually because the meson subproject doesn't support building for Android platform. It needs a recent RC release because latest stable release is 4 years old and fails to build. Fixes #1385.
2018-05-20 06:14:56 +02:00
paths:
ci: Be consistent on artifact naming
2018-06-05 20:01:53 +02:00
- "_build/meson-logs"
Add Android CI This adds to the CI a cross build for Android NDK r16 API 21 (because thats what GStreamer currently use) for arm64. GNU iconv must be built manually into our docker image because Android NDK doesn't seems to ship it. The latest NDK r17 API 28 has iconv.h but iconv_open() symbol isn't found by the linker. Looks like broken NDK. libffi also needs to be built manually because the meson subproject doesn't support building for Android platform. It needs a recent RC release because latest stable release is 4 years old and fails to build. Fixes #1385.
2018-05-20 06:14:56 +02:00
ci: factor out cross compilation jobs definitions
2018-06-27 15:14:38 +02:00
cross-android_api21_arm64:
<<: *cross-template
ci: Move to per-job images We don't use a global Docker image any more.
2019-04-30 15:01:28 +02:00
image: registry.gitlab.gnome.org/gnome/glib/android-ndk:v1
ci: factor out cross compilation jobs definitions
2018-06-27 15:14:38 +02:00
script:
# FIXME: add --werror
ci: The iconv combo option values have changed
2019-04-04 01:55:58 +02:00
# We use -Diconv=auto to test that we successfully detect that iconv is not
# provided by android api 21, and detect the external iconv instead.
- meson ${MESON_COMMON_OPTIONS} --cross-file=/opt/cross_file_android_arm64_21.txt -Diconv=auto -Dinternal_pcre=true _build
ci: factor out cross compilation jobs definitions
2018-06-27 15:14:38 +02:00
- ninja -C _build
ci: Add latest Android API level 28 - Split the download part into a separate script to so docker keeps that step in cache and avoid redownloading it. - With API level >= 28 libiconv is not needed anymore because it's part of Android's libc. - Generate standalone toolchains to reduce the docker image size. It's also easier because it doesn't need to pass sysroot args. - Use clang compiler because gcc is deprecated in this Android NDK and will be removed in the next release.
2018-06-26 19:18:29 +02:00
cross-android_api28_arm64:
<<: *cross-template
ci: Move to per-job images We don't use a global Docker image any more.
2019-04-30 15:01:28 +02:00
image: registry.gitlab.gnome.org/gnome/glib/android-ndk:v1
ci: Add latest Android API level 28 - Split the download part into a separate script to so docker keeps that step in cache and avoid redownloading it. - With API level >= 28 libiconv is not needed anymore because it's part of Android's libc. - Generate standalone toolchains to reduce the docker image size. It's also easier because it doesn't need to pass sysroot args. - Use clang compiler because gcc is deprecated in this Android NDK and will be removed in the next release.
2018-06-26 19:18:29 +02:00
script:
# FIXME: add --werror
ci: Upgrade meson to 0.48.0 and use --fatal-meson-warnings
2018-09-24 16:19:18 +02:00
- meson ${MESON_COMMON_OPTIONS} --cross-file=/opt/cross_file_android_arm64_28.txt -Dinternal_pcre=true _build
ci: Add latest Android API level 28 - Split the download part into a separate script to so docker keeps that step in cache and avoid redownloading it. - With API level >= 28 libiconv is not needed anymore because it's part of Android's libc. - Generate standalone toolchains to reduce the docker image size. It's also easier because it doesn't need to pass sysroot args. - Use clang compiler because gcc is deprecated in this Android NDK and will be removed in the next release.
2018-06-26 19:18:29 +02:00
- ninja -C _build
ci: Use shorter job names Job names in gitlab pipeline view gets truncated to "fedora-meson-..." for all jobs which is not really useful. All our CIs are using Meson, and the host distro is not relevant when doing cross builds.
2018-06-22 17:08:06 +02:00
cross-mingw64:
ci: factor out cross compilation jobs definitions
2018-06-27 15:14:38 +02:00
<<: *cross-template
ci: Move to per-job images We don't use a global Docker image any more.
2019-04-30 15:01:28 +02:00
image: registry.gitlab.gnome.org/gnome/glib/mingw:v1
Add mingw64 cross build CI Fixes #1387.
2018-05-20 21:17:48 +02:00
script:
# FIXME: Add --werror
ci: Upgrade meson to 0.48.0 and use --fatal-meson-warnings
2018-09-24 16:19:18 +02:00
- meson ${MESON_COMMON_OPTIONS} --cross-file=/opt/cross_file_mingw64.txt _build
Add mingw64 cross build CI Fixes #1387.
2018-05-20 21:17:48 +02:00
- ninja -C _build
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
msys2-mingw32:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
stage: build
tags:
- win32
variables:
MSYSTEM: "MINGW32"
CHERE_INVOKING: "yes"
script:
- C:\msys64\usr\bin\pacman --noconfirm -Syyuu --ask 20
- C:\msys64\usr\bin\bash -lc "bash -x ./.gitlab-ci/test-msys2.sh"
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
artifacts:
ci: Run test coverage for MSYS2 job
2019-04-06 16:22:04 +02:00
reports:
junit: "_build/%CI_JOB_NAME%-report.xml"
ci: Clarify artifact naming Put the job name and commit identifier in the artifact names. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-29 11:54:29 +02:00
name: "glib-%CI_JOB_NAME%-%CI_COMMIT_REF_NAME%"
ci: Export meson-logs from msys2-mingw32 build as artifacts This means that compilation and test failures will leave logs on the CI machines which we can use to debug the failures. Always export the artifacts. The default `when: on_success` is appropriate for now, but won’t be in future when the tests actual report their success value correctly. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-28 14:11:22 +02:00
when: always
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
paths:
ci: Export meson-logs from msys2-mingw32 build as artifacts This means that compilation and test failures will leave logs on the CI machines which we can use to debug the failures. Always export the artifacts. The default `when: on_success` is appropriate for now, but won’t be in future when the tests actual report their success value correctly. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-28 14:11:22 +02:00
- _build/meson-logs
ci: Run test coverage for MSYS2 job
2019-04-06 16:22:04 +02:00
- "_build/%CI_JOB_NAME%-report.xml"
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
- _coverage/
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed.
2018-05-24 19:18:25 +02:00
vs2017-x64:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed.
2018-05-24 19:18:25 +02:00
stage: build
tags:
- win32
script:
- .gitlab-ci/test-msvc.bat
artifacts:
CI: Run test coverage for Visual Studio builds Ensure that we do run it and upload the results.
2019-04-08 10:51:47 +02:00
reports:
junit: "_build/%CI_JOB_NAME%-report.xml"
ci: Clarify artifact naming Put the job name and commit identifier in the artifact names. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-29 11:54:29 +02:00
name: "glib-%CI_JOB_NAME%-%CI_COMMIT_REF_NAME%"
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed.
2018-05-24 19:18:25 +02:00
when: always
paths:
- _build/meson-logs
CI: Run test coverage for Visual Studio builds Ensure that we do run it and upload the results.
2019-04-08 10:51:47 +02:00
- "_build/%CI_JOB_NAME%-report.xml"
ci: Add a VS2017 job Thanks to Xavier Claessens for figuring out what is needed.
2018-05-24 19:18:25 +02:00
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
freebsd-11-x86_64:
stage: build
ci: Enable FreeBSD CI in the official repository Since we are unable to promote our FreeBSD runner to a shared runner, we can only enable it in GNOME group. This should avoid problems when submitting merge requests from forks.
2018-10-09 16:54:48 +02:00
only:
- branches@GNOME/glib
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
tags:
# To run a FreeBSD builder, install gitlab-runner package and start both
# gitlab-runner and dbus service because we need /var/lib/dbus/machine-id.
# To compile GLib, you still have to install the following packages:
# desktop-file-utils gettext libiconv meson pkgconf python3 shared-mime-info
- freebsd-11
variables:
# CPPFLAGS is required because libintl doesn't use pkg-config.
CPPFLAGS: -I/usr/local/include
# FIXME: Workaround meson inability to set LD_LIBRARY_PATH.
# https://github.com/mesonbuild/meson/issues/1383
# https://github.com/mesonbuild/meson/issues/1635
# https://github.com/mesonbuild/meson/issues/2881
LDFLAGS: -L/usr/local/lib -Wl,--disable-new-dtags
# FreeBSD doesn't have C.UTF-8 locale.
LANG: en_US.UTF-8
script:
# We cannot use -Wl,--no-undefined because GLib uses 'environ' variable.
ci: The iconv combo option values have changed
2019-04-04 01:55:58 +02:00
# FreeBSD iconv doesn't handle transliteration, so we use (external) GNU libiconv here.
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
# FreeBSD supports xattr, but its API is different from Linux xattr.
# FIXME: extattr(2) support: https://gitlab.gnome.org/GNOME/glib/issues/1404
ci: The iconv combo option values have changed
2019-04-04 01:55:58 +02:00
- meson ${MESON_COMMON_OPTIONS} -Db_lundef=false -Diconv=external -Dxattr=false _build
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
- ninja -C _build
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
- bash -x ./.gitlab-ci/run-tests.sh
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
artifacts:
ci: Enable CI on FreeBSD 12
2019-06-24 16:55:36 +02:00
reports:
junit: "_build/${CI_JOB_NAME}-report.xml"
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
paths:
- "_build/config.h"
- "_build/glib/glibconfig.h"
- "_build/meson-logs"
- "_build/${CI_JOB_NAME}-report.xml"
freebsd-12-x86_64:
stage: build
only:
- branches@GNOME/glib
tags:
- freebsd-12
variables:
CPPFLAGS: -I/usr/local/include
LDFLAGS: -L/usr/local/lib -Wl,--disable-new-dtags
LANG: en_US.UTF-8
script:
- meson ${MESON_COMMON_OPTIONS} -Db_lundef=false -Diconv=external -Dxattr=false _build
- ninja -C _build
- bash -x ./.gitlab-ci/run-tests.sh
except:
- tags
artifacts:
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
reports:
junit: "_build/${CI_JOB_NAME}-report.xml"
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
paths:
ci: Enable FreeBSD CI
2018-09-28 19:01:12 +02:00
- "_build/config.h"
- "_build/glib/glibconfig.h"
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
- "_build/meson-logs"
ci: Generate a cover report for the test suite GitLab can show the results of a CI pipeline if the pipeline generates a report using the JUnit XML format. Since Meson provides a machine parseable output for `meson test`, we can take that and turn it into XML soup.
2019-04-05 21:53:11 +02:00
- "_build/${CI_JOB_NAME}-report.xml"
ci: Add FreeBSD CI We use 'freebsd-11' instead of 'freebsd' as tags here because newer FreeBSD versions can include API changes which are worth testing.
2018-05-24 17:14:25 +02:00
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
coverage:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Use new Fedora v5 Docker image for all CI jobs v5 was built using the fedora.Dockerfile updates from the previous few commits. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 14:22:26 +01:00
image: registry.gitlab.gnome.org/gnome/glib/fedora:v5
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
stage: coverage
artifacts:
ci: Clarify artifact naming Put the job name and commit identifier in the artifact names. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-29 11:54:29 +02:00
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
paths:
- _coverage/
script:
- bash -x ./.gitlab-ci/coverage-docker.sh
ci: Add a regex to parse line coverage statistics from genhtml output GitLab can then use this to annotate each pipeline with its code coverage statistics. It can only use one figure, so we choose lines (rather than function or branch coverage) since it’s the most intuitive figure. This parses the ‘lines’ line from output like: Overall coverage rate: lines......: 76.7% (108959 of 142122 lines) functions..: 80.7% (10294 of 12763 functions) branches...: 51.3% (50226 of 97953 branches) Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-05-25 00:43:03 +02:00
coverage: '/^\s+lines\.+:\s+([\d.]+\%)\s+/'
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
ci: Add scan-build job in a new ‘analysis’ pipeline stage Use Meson’s support for running scan-build (Clang’s static analyser) against the build, so that we get static analysis of each pipeline. Add it in a new pipeline stage, after code coverage, so that we don’t waste resources on it unless the unit tests pass — a static analysis build takes perhaps 10× as long as a normal GCC build. https://mesonbuild.com/howtox.html#use-clang-static-analyzer Currently, the static analysis results are uploaded as artifacts, but the job will always succeed (regardless of whether there are any bugs found in the analysis). Currently, a large number of reports are outputted by the analyser, which need to be fixed before we can gate the pipeline on it. Furthermore, in order to get scan-build to exit with a non-zero status if any bugs are found, we need to depend on Meson ≥ 0.49.0, which contains the fix https://github.com/mesonbuild/meson/issues/4334, allowing us to add the following to .gitlab-ci.yml: ``` variables: # Exit with a non-zero status if any bugs are found SCANBUILD: "scan-build --status-bugs" ``` Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-12-28 00:32:39 +01:00
scan-build:
ci: Use extends rather than YAML anchors for `only-default` This makes things slightly more extensible in future, but introduces no functional differences right now. See https://docs.gitlab.com/ce/ci/yaml/README.html#extends. Suggested by Jordan Petridis. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-28 12:38:25 +01:00
extends: .only-default
ci: Use new Fedora v5 Docker image for all CI jobs v5 was built using the fedora.Dockerfile updates from the previous few commits. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 14:22:26 +01:00
image: registry.gitlab.gnome.org/gnome/glib/fedora:v5
ci: Add scan-build job in a new ‘analysis’ pipeline stage Use Meson’s support for running scan-build (Clang’s static analyser) against the build, so that we get static analysis of each pipeline. Add it in a new pipeline stage, after code coverage, so that we don’t waste resources on it unless the unit tests pass — a static analysis build takes perhaps 10× as long as a normal GCC build. https://mesonbuild.com/howtox.html#use-clang-static-analyzer Currently, the static analysis results are uploaded as artifacts, but the job will always succeed (regardless of whether there are any bugs found in the analysis). Currently, a large number of reports are outputted by the analyser, which need to be fixed before we can gate the pipeline on it. Furthermore, in order to get scan-build to exit with a non-zero status if any bugs are found, we need to depend on Meson ≥ 0.49.0, which contains the fix https://github.com/mesonbuild/meson/issues/4334, allowing us to add the following to .gitlab-ci.yml: ``` variables: # Exit with a non-zero status if any bugs are found SCANBUILD: "scan-build --status-bugs" ``` Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-12-28 00:32:39 +01:00
stage: analysis
script:
- meson ${MESON_COMMON_OPTIONS}
--werror
--default-library=both
--prefix=$HOME/glib-installed
--libdir=lib
-Dsystemtap=true
-Ddtrace=true
-Dfam=true
-Dinstalled_tests=true
ci: Run scan-build in a different build directory The build artifacts from earlier jobs in the pipeline all use the `_build` directory. When they are copied in to the scan-build job, they are probably marked as read-only. This means that the `meson scan-build` run can’t write to `_build/meson-logs/meson-log.txt` and fails. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-06-12 15:31:42 +02:00
_scan_build
- ninja -C _scan_build scan-build
ci: Add scan-build job in a new ‘analysis’ pipeline stage Use Meson’s support for running scan-build (Clang’s static analyser) against the build, so that we get static analysis of each pipeline. Add it in a new pipeline stage, after code coverage, so that we don’t waste resources on it unless the unit tests pass — a static analysis build takes perhaps 10× as long as a normal GCC build. https://mesonbuild.com/howtox.html#use-clang-static-analyzer Currently, the static analysis results are uploaded as artifacts, but the job will always succeed (regardless of whether there are any bugs found in the analysis). Currently, a large number of reports are outputted by the analyser, which need to be fixed before we can gate the pipeline on it. Furthermore, in order to get scan-build to exit with a non-zero status if any bugs are found, we need to depend on Meson ≥ 0.49.0, which contains the fix https://github.com/mesonbuild/meson/issues/4334, allowing us to add the following to .gitlab-ci.yml: ``` variables: # Exit with a non-zero status if any bugs are found SCANBUILD: "scan-build --status-bugs" ``` Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-12-28 00:32:39 +01:00
artifacts:
name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
paths:
ci: Run scan-build in a different build directory The build artifacts from earlier jobs in the pipeline all use the `_build` directory. When they are copied in to the scan-build job, they are probably marked as read-only. This means that the `meson scan-build` run can’t write to `_build/meson-logs/meson-log.txt` and fails. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-06-12 15:31:42 +02:00
- "_scan_build/meson-logs/scanbuild"
ci: Add scan-build job in a new ‘analysis’ pipeline stage Use Meson’s support for running scan-build (Clang’s static analyser) against the build, so that we get static analysis of each pipeline. Add it in a new pipeline stage, after code coverage, so that we don’t waste resources on it unless the unit tests pass — a static analysis build takes perhaps 10× as long as a normal GCC build. https://mesonbuild.com/howtox.html#use-clang-static-analyzer Currently, the static analysis results are uploaded as artifacts, but the job will always succeed (regardless of whether there are any bugs found in the analysis). Currently, a large number of reports are outputted by the analyser, which need to be fixed before we can gate the pipeline on it. Furthermore, in order to get scan-build to exit with a non-zero status if any bugs are found, we need to depend on Meson ≥ 0.49.0, which contains the fix https://github.com/mesonbuild/meson/issues/4334, allowing us to add the following to .gitlab-ci.yml: ``` variables: # Exit with a non-zero status if any bugs are found SCANBUILD: "scan-build --status-bugs" ``` Signed-off-by: Philip Withnall <withnall@endlessm.com>
2018-12-28 00:32:39 +01:00
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
pages:
stage: deploy
ci: Add missing "except: tags"
2018-06-05 19:39:26 +02:00
only:
- master
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
script:
- mv _coverage/ public/
artifacts:
paths:
- public
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
dist-job:
ci: Use new Fedora v5 Docker image for all CI jobs v5 was built using the fedora.Dockerfile updates from the previous few commits. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2019-11-27 14:22:26 +01:00
image: registry.gitlab.gnome.org/gnome/glib/fedora:v5
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
stage: build
only:
- tags
script:
ci: Upgrade meson to 0.48.0 and use --fatal-meson-warnings
2018-09-24 16:19:18 +02:00
- meson --buildtype release --fatal-meson-warnings -Dgtk_doc=true -Dman=true _build
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
- cd _build
- ninja dist
ci: Fix dist-job missing gobject/gio documentation This requires meson >= 0.47.0 otherwise building the doc fails: https://github.com/mesonbuild/meson/issues/3379 While at it, no need to to pass --prefix --libdir to meson, other CIs don't have them.
2018-06-18 15:47:39 +02:00
- ninja glib-doc gobject-doc gio-doc
ci: Add GitLab CI description file We're mostly interested into building and testing everything that gets pushed to the repository — including merge requests. When pushing tags, though, we should assume we're spinning a release, so let's run the dist target, and store the tarball, and the generated documentation while we're at it, as artifacts on GitLab. The Dockerfile for the image used for the build is included in tree, and published on Docker Hub. Using a custom image allows us to avoid the costly "download and install build dependencies" phase, as well as controlling the environment a little bit better. https://bugzilla.gnome.org/show_bug.cgi?id=793635
2018-02-18 15:59:29 +01:00
- tar -c -f "glib-docs-$CI_COMMIT_TAG.tar.xz" -C docs/reference/glib html
- tar -c -f "gobject-docs-$CI_COMMIT_TAG.tar.xz" -C docs/reference/gobject html
- tar -c -f "gio-docs-$CI_COMMIT_TAG.tar.xz" -C docs/reference/gio html
artifacts:
paths:
- "${CI_PROJECT_DIR}/_build/glib-docs.tar.xz"
- "${CI_PROJECT_DIR}/_build/gobject-docs.tar.xz"
- "${CI_PROJECT_DIR}/_build/gio-docs.tar.xz"
- "${CI_PROJECT_DIR}/_build/meson-dist/glib-*.tar.xz"
Reference in New Issue Copy Permalink