luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-07 01:46:16 +01:00
Code Issues Packages Projects Releases Wiki Activity
b7203e9406
glib/.gitlab-ci/fedora.Dockerfile

107 lines
2.1 KiB
Docker
Raw Normal View History

ci: Update Fedora CI image to Fedora 39 Fedora 37 is out of support so, as per our policy, update the CI image to the oldest still-supported release, which is 39. Update the mingw CI image too, as it’s built on top of the Fedora one. Update the supported platforms documentation (and fix the Debian version listed there to match what’s currently in CI, which is up to date). Signed-off-by: Philip Withnall <pwithnall@gnome.org>
2024-05-15 11:33:00 +02:00
FROM fedora:39
ci: Ensure the machine-id is set on the Fedora CI image Run `systemd-machine-id-setup` when creating the image, so that `/etc/machine-id` is created with a valid ID. Since systemd isn’t started when running the CI image with podman/Docker, it’s not created otherwise. This causes some tests to fail. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2021-03-01 14:55:03 +01:00
ci: Update Fedora image before installing new items This fixes some scriptlets crashes during package installation.
2020-01-17 10:06:36 +01:00
RUN dnf -y update \
&& dnf -y install \
ci: add bindfs and fuse to Fedora CI image Without `bindfs` and `fusermount`, all tests in g-file-info-filesystem-readonly.c are skipped.
2018-11-12 13:44:19 +01:00
bindfs \
ci: Add clang and scan-build We want to run the Clang-based build analysis tool in our CI pipeline, taking advantage of its native support in Meson.
2019-04-29 16:24:46 +02:00
clang \
clang-analyzer \
ci: Remove Android and MingW bits from the fedora Dockerfile These live in their own Dockerfiles, now.
2019-04-30 14:24:04 +02:00
dbus-daemon \
ci: Add libdbus development files to CI Docker images We use these to test interoperability between libdbus and GDBus. Signed-off-by: Simon McVittie <smcv@collabora.com>
2019-10-21 17:45:01 +02:00
dbus-devel \
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
desktop-file-utils \
elfutils-libelf-devel \
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
findutils \
ci: add bindfs and fuse to Fedora CI image Without `bindfs` and `fusermount`, all tests in g-file-info-filesystem-readonly.c are skipped.
2018-11-12 13:44:19 +01:00
fuse \
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
gcc \
gcc-c++ \
ci: Add gdb to some CI images This will be useful in general, for manually debugging failures if we need (without having to rebuild the CI images to do so). It will also be useful for the `assert-msg-test` test, which is being reworked in !2767. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Helps: #1434
2022-06-24 13:52:03 +02:00
gdb \
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
gettext \
docs: Add initial support for using gi-docgen for docs The files here are copied from the docs-gtk-org branch of gtk. This adds gi-docgen to the CI Dockerfiles and ensures the new versions (including the OS upgrades from the previous commit) are used during CI. Helps: #3037
2023-10-10 00:04:21 +02:00
gi-docgen \
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
git \
glibc-devel \
fixup! ci: Upgrade CI images to the new oldest-supported OS versions This was accidentally missed out of the above commit, due to pushing a new version of the image to test, without also pushing the git branch.
2023-10-11 17:33:27 +02:00
glibc-gconv-extra \
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
glibc-headers \
ci: Install additional locales used during tests Note that this intentionally does not use glibc-all-langpacks package since its contents is currently incomplete. https://bugzilla.redhat.com/show_bug.cgi?id=1624528
2018-12-03 01:00:00 +01:00
glibc-langpack-de \
glibc-langpack-el \
glibc-langpack-en \
glibc-langpack-es \
glibc-langpack-fa \
glibc-langpack-fr \
gdatetime: Fix incorrect alt-digits being used after changing locale The alt-digits are loaded from `nl_langinfo()` in a `GOnce` section, which means `nl_langinfo()` is not re-queried after the process changes locale (if that happens). So, change the `GOnce` to a mutex and store the locale of the alt-digits alongside them. This will introduce contention when calling `format_number()` is called, but how often are multiple threads trying to format dates at the same time? If this does get highlighted as a performance problem, the other approach I considered was a `GPrivate` struct containing all the locale-specific cached data. That comes at the cost of using a `GPrivate` slot (although that’s only particularly expensive on Windows, and the locale code is quite different for Windows, so perhaps that could be avoided entirely). It does mean that all locale printing could be lock-free and still safely update cached data on a locale change. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2023-10-18 16:52:07 +02:00
glibc-langpack-gu \
ci: Install additional locales used during tests Note that this intentionally does not use glibc-all-langpacks package since its contents is currently incomplete. https://bugzilla.redhat.com/show_bug.cgi?id=1624528
2018-12-03 01:00:00 +01:00
glibc-langpack-hr \
glibc-langpack-ja \
glibc-langpack-lt \
glibc-langpack-pl \
glibc-langpack-ru \
gdatetime: Add support for %E modifier to g_date_time_format() The `%E` modifier causes dates to be formatted using an alternative era representation for years. This doesn’t do anything for most dates, but in locales such as Thai and Japanese it causes years to be printed using era names. In Thai, this means the Thai solar calendar (https://en.wikipedia.org/wiki/Thai_solar_calendar). In Japanese, this means Japanese era names (https://en.wikipedia.org/wiki/Japanese_era_name). The `%E` modifier syntax follows what’s supported in glibc — see nl_langinfo(3). Supporting this is quite involved, as it means loading the `ERA` description from libc and parsing it. Unit tests are included. Signed-off-by: Philip Withnall <philip@tecnocode.co.uk> Fixes: #3119
2023-10-18 16:50:57 +02:00
glibc-langpack-th \
ci: Install additional locales used during tests Note that this intentionally does not use glibc-all-langpacks package since its contents is currently incomplete. https://bugzilla.redhat.com/show_bug.cgi?id=1624528
2018-12-03 01:00:00 +01:00
glibc-langpack-tr \
ci: Require some updated packages Fedora Docker image Rather than installing those updates manually.
2019-12-11 17:47:45 +01:00
"gnome-desktop-testing >= 2018.1" \
ci: Build with introspection enabled In most CI builds. (Not all of them, though, so we can also test the build works with it disabled.) This is needed for the upcoming libgirepository tests, as they need some GIR files to test against. Signed-off-by: Philip Withnall <pwithnall@gnome.org> Helps: #3155
2023-11-28 19:00:35 +01:00
gobject-introspection \
gobject-introspection-devel \
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
gtk-doc \
itstool \
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
lcov \
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
libattr-devel \
libffi-devel \
libmount-devel \
libselinux-devel \
libxslt \
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
ncurses-compat-libs \
ci: Install Meson from PyPI The base Fedora image we use for our CI does not always have an updated Meson package to fit our requirements. Let's install Meson using Python's pip instead.
2018-03-29 10:57:55 +02:00
ninja-build \
ci: Add libpcre2 dependencies and subproject This is in preparation for porting `GRegex` to libpcre2, which is happening in !2529. It’s a big port, though, and specially rebuilding the CI images to add libpcre2 for it is a pain. Add libpcre2, and then !2529 can drop the old libpcre dependencies when the port lands. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Helps: #1085
2022-06-24 13:50:26 +02:00
pcre2-devel \
ci: Require some updated packages Fedora Docker image Rather than installing those updates manually.
2019-12-11 17:47:45 +01:00
"python3-dbusmock >= 0.18.3-2" \
build: Change default for -Dman-pages from disabled to auto Previously, `-Dman=false` was the default, because the generated man pages were shipped in the distribution tarball already, so the option actually mostly controlled whether to *re*build them. The generated pages are no longer shipped in the tarball (and probably haven’t been since the port to Meson, though I haven’t checked), so it makes sense to change the default to encourage building the man pages if the right tooling (`rst2man`) is available. Signed-off-by: Philip Withnall <pwithnall@gnome.org>
2023-12-21 14:35:18 +01:00
python3-docutils \
ci: Add python3-pip to Fedora dependencies It’s needed to provide the `pip3` executable, which the `Dockerfile` later uses. Follow-up to !1464. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2020-05-07 14:22:02 +02:00
python3-pip \
ci: Update Meson to 0.52.1 in fedora docker 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.
2019-12-13 19:54:28 +01:00
python3-pygments \
ci: Install Meson from PyPI The base Fedora image we use for our CI does not always have an updated Meson package to fit our requirements. Let's install Meson using Python's pip instead.
2018-03-29 10:57:55 +02:00
python3-wheel \
ci: Remove Android and MingW bits from the fedora Dockerfile These live in their own Dockerfiles, now.
2019-04-30 14:24:04 +02:00
shared-mime-info \
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
systemtap-sdt-devel \
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
unzip \
ci: Add valgrind to fedora Docker image It will be used in an upcoming commit. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #487
2019-08-21 23:48:53 +02:00
valgrind \
Dockerfile: Reorder packages in alphabetical order
2018-06-07 17:27:54 +02:00
wget \
ci: Install some missing packages in fedora docker image
2020-01-13 18:46:01 +01:00
xdg-desktop-portal \
ci: Add an autotools job
2018-08-23 21:53:29 +02:00
xz \
Dockerfile: Reorder packages in alphabetical order
2018-06-07 17:27:54 +02:00
zlib-devel \
ci: Install build deps for extra modules in Docker image Rather than bringing build dependencies for gobject-introspection and xdg-desktop-portal manually, install them in the Docker image.
2019-12-11 17:48:24 +01:00
&& dnf -y install \
meson \
flex \
bison \
python3-devel \
autoconf \
automake \
gettext-devel \
libtool \
diffutils \
fontconfig-devel \
json-glib-devel \
geoclue2-devel \
pipewire-devel \
fuse-devel \
make \
ci: Install Meson from PyPI The base Fedora image we use for our CI does not always have an updated Meson package to fit our requirements. Let's install Meson using Python's pip instead.
2018-03-29 10:57:55 +02:00
&& dnf clean all
build: Bump Meson dependency to 1.2.0 And update all the CI builds to use the latest micro release from that series, 1.2.3. This version bump means we can: - Drop some backwards-compatibility Meson checks - Fix a periodic CI failure caused by a now-fixed Meson bug (https://github.com/mesonbuild/meson/pull/10633) It’s in line with our [Meson version policy](./docs/meson-version.md), as Meson 1.2.1 is available in [Debian Trixie](https://packages.debian.org/source/trixie/meson) and the [freedesktop SDK](https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/blob/c95902f2ed5cb7d9b8e352135facc539029ef6c9/elements/components/meson.bst). Signed-off-by: Philip Withnall <philip@tecnocode.co.uk>
2023-10-24 17:46:36 +02:00
RUN pip3 install meson==1.2.3
ci: Pin meson version to 0.46.1 when generating docker image Also move it after running setup-android-ndk.sh so docker can keep that stage in cache and won't run it again when changing meson version.
2018-06-22 17:02:02 +02:00
ci: Install lcov-cobertura and cobertura-split script in coverage images These are needed to be able to get cobertura reports in gitlab.
2022-09-15 02:22:41 +02:00
COPY install-gitlab-cobertura-tools.sh .
RUN ./install-gitlab-cobertura-tools.sh
ci: Update Fedora CI images to new oldstable (33) Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2021-10-07 17:29:31 +02:00
# Set /etc/machine-id as it’s needed for some D-Bus tests
RUN systemd-machine-id-setup
ci: Add sudo support for default Fedora docker user
2019-11-20 14:54:09 +01:00
# Enable sudo for wheel users
RUN sed -i -e 's/# %wheel/%wheel/' -e '0,/%wheel/{s/%wheel/# %wheel/}' /etc/sudoers
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
ARG HOST_USER_ID=5555
ENV HOST_USER_ID ${HOST_USER_ID}
ci: Add sudo support for default Fedora docker user
2019-11-20 14:54:09 +01:00
RUN useradd -u $HOST_USER_ID -G wheel -ms /bin/bash user
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: Update to latest Android NDK Move the NDK in the common Fedora image, better have 1 bigger image that gets cached into runners. It is also less images to maintain. Fixes: #2605
2022-04-26 16:50:36 +02:00
COPY android-ndk.sh .
RUN ./android-ndk.sh
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
USER user
WORKDIR /home/user
ci: Cache subprojects in docker images
2020-01-13 18:31:15 +01:00
COPY cache-subprojects.sh .
RUN ./cache-subprojects.sh
ci: Install Meson from PyPI The base Fedora image we use for our CI does not always have an updated Meson package to fit our requirements. Let's install Meson using Python's pip instead.
2018-03-29 10:57:55 +02:00
ENV LANG C.UTF-8
Reference in New Issue Copy Permalink