1. 27 Jul, 2020 1 commit
  2. 25 Jun, 2020 1 commit
  3. 22 May, 2020 1 commit
  4. 07 May, 2020 2 commits
  5. 29 Apr, 2020 1 commit
    • Christoph Reiter's avatar
      CI: Switch to new Windows runners · c3645a84
      Christoph Reiter authored
      gitlab will drop cmd.exe support with GitLab 13 so I took the opportunity to
      add new runners with Windows 2016 and powershell as default.
      
      These runners are tagged with win32-ps instead of win32. The old runners
      will be switched off in the coming weeks.
      
      The main difference is that all commands and env expansions use powershell
      and Windows 2016 instead of 2012r2.
      c3645a84
  6. 09 Apr, 2020 1 commit
    • Xavier Claessens's avatar
      Meson: Add glib_checks and glib_asserts options · be3728b9
      Xavier Claessens authored
      In cases where performance are critical it can be useful to disable
      checks and asserts. GStreamer has those options too, using the same name
      and setting them yielding means we can set those options on the main
      project (e.g. gst-build) and glib will inherit the same value when built
      as subproject.
      be3728b9
  7. 04 Mar, 2020 1 commit
  8. 02 Mar, 2020 1 commit
  9. 24 Feb, 2020 1 commit
  10. 21 Feb, 2020 2 commits
    • Bastien Nocera's avatar
      ci: Fix xdg-desktop-portal build · f333a805
      Bastien Nocera authored
      Newer versions of xdg-desktop-portal need a newer PipeWire, so use the
      latest release that doesn't contain this change to avoid having
      something else to build.
      f333a805
    • Bastien Nocera's avatar
      ci: Don't ignore xdg-desktop-portal build failure · 7263fc55
      Bastien Nocera authored
      CI scripts are done using a shell with 'set -e' enabled, but using
      '&&' means that the line won't "fail". Run the different commands
      sequentially instead.
      
      Spotted by Simon McVittie <smcv@collabora.com>
      
      Closes: #2043
      7263fc55
  11. 04 Feb, 2020 3 commits
  12. 29 Jan, 2020 2 commits
    • Xavier Claessens's avatar
      ci: Update Meson to 0.52.1 in fedora docker · 47a20304
      Xavier Claessens authored
      This is required to be able to build the doc. The debian docker is still
      pinned to 0.49.2 which ensure we can build with both versions of meson.
      
      Meson 0.52.0 warns about adding -Wall flag manually, we can remove that
      because warning_level=1 (the default) option already implies it.
      47a20304
    • Xavier Claessens's avatar
      doc: Run gtkdoc-check with unit tests · 09d99528
      Xavier Claessens authored
      This has the side effect of always rebuilding the doc at each build when
      gtk_doc option is enabled (not by default). Most importantly, this will
      enable doc check on our CI.
      09d99528
  13. 21 Jan, 2020 1 commit
  14. 20 Jan, 2020 1 commit
  15. 16 Jan, 2020 5 commits
  16. 07 Jan, 2020 1 commit
  17. 16 Dec, 2019 1 commit
  18. 12 Dec, 2019 1 commit
    • Bastien Nocera's avatar
      ci: Fix permission error in valgrind analysis stage · 5a174d10
      Bastien Nocera authored
      The valgrind analysis stage inherits from existing artefacts, so make
      sure to reset the permissions on the glib build directory to avoid a new
      build failing.
      
      $ meson ${MESON_COMMON_OPTIONS} --werror -Dsystemtap=true -Ddtrace=true -Dfam=true -Dinstalled_tests=true _build
      <snip>
      PermissionError: [Errno 13] Permission denied: '/builds/GNOME/glib/_build/meson-logs/meson-log.txt'
      5a174d10
  19. 11 Dec, 2019 6 commits
  20. 04 Dec, 2019 3 commits
  21. 28 Nov, 2019 2 commits
  22. 27 Nov, 2019 2 commits
    • Philip Withnall's avatar
      ci: Use new Fedora v5 Docker image for all CI jobs · cd11067a
      Philip Withnall authored
      v5 was built using the fedora.Dockerfile updates from the previous few
      commits.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      cd11067a
    • Philip Withnall's avatar
      ci: Fix running all jobs on merge requests · 2daebc76
      Philip Withnall authored
      Since we added `only: [merge_requests]` for the `style-check-diff` job,
      that started running detached pipelines only for merge requests and only
      containing that job, and not running the other jobs for merge requests
      (only for branches).
      
      That wasn’t the intention.
      
      Follow the guide on
      https://docs.gitlab.com/ee/ci/merge_request_pipelines/index.html#excluding-certain-jobs
      to ensure that all jobs (including `style-check-diff`) are run for merge
      requests.
      
      This means we can no longer unconditionally use
      `${CI_MERGE_REQUEST_TARGET_BRANCH_{NAME,SHA}}`, since they are only
      defined for jobs which are running against a merge request rather than a
      branch. Instead, use some `git rev-list` magic from
      https://stackoverflow.com/a/4991675/2931197 to find the newest common
      ancestor commit between the detached head that CI is running on, and the
      known or likely target branch. Do the style check against the diff
      between the newest common ancestor commit and the detached head.
      
      (Note that `${CI_MERGE_REQUEST_TARGET_BRANCH_SHA}` was never actually
      defined for any of our pipelines, since it’s only available for CI
      pipelines running on merged branches, which is a GitLab Premium
      feature. Oops, my bad.)
      
      In order to find the newest common ancestor commit, we need to pull the
      upstream remote, since the CI pipeline might be running on a fork of the
      main repository where various branches (particularly `master`) are out
      of date.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      2daebc76