dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gimp/.gitlab-ci.yml

348 lines
11 KiB
YAML
Raw Normal View History

gitlab-ci: port our main CI to Debian testing. The old custom ArchLinux got broken (apparently by some package signature verification which fails, and obviously we don't want to bypass these for security reasons). I took the opportunity to port to Debian testing because this is GIMP's base distribution for support (basically dependency versions must be in Debian testing) so it makes sense that our CI is based off it as well. Note though that I am not against additional CI tests so if someone absolutely wants to get the Archlinux-based CI back and thinks it gets us some additional worthy test, feel free to fix whatever was broken then we may add it back (having both Debian testing and Archlinux CI).
2020-01-02 02:57:06 +08:00
image: debian:testing
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
stages:
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
- prepare
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
- dependencies
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
- gimp
gitlab-ci: add an analysis stage with cppcheck code analysis stage. As contributed by Rafał @qarmin in a Gitlab comment. See #5002.
2020-04-29 00:39:32 +08:00
- analysis
gitlab-ci: add a distribution step. I don't add this at the end of the distcheck job to make the interface clearer, and also because the distcheck job will have full build artifacts (allowing to debug a failing distcheck if necessary), whereas the `sources` job will just publish tarballs and SHA256 sums generated from these tarballs. Simple, clean.
2020-08-07 22:41:05 +08:00
- distribution
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
variables:
gitlab-ci: set GIT_DEPTH to 1. We don't need to pull 5 commits of history. Only the HEAD of the selected branch is needed. Also define it globally rather than re-defining it in every job to the same value.
2019-10-02 02:36:09 +08:00
GIT_DEPTH: "1"
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
INSTALL_DIR: "_install"
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
INSTALL_PREFIX: "${CI_PROJECT_DIR}/${INSTALL_DIR}"
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
APT_CACHE: "${CI_PROJECT_DIR}/apt-cache"
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
## prepare docker images ##
build-image:
stage: prepare
variables:
GIT_STRATEGY: none
cache: {}
image:
name: gcr.io/kaniko-project/executor:debug
entrypoint: [""]
script:
- mkdir -p /kaniko/.docker
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
- echo "FROM debian:testing" > Dockerfile
- echo "RUN apt-get update" >> Dockerfile
- echo "RUN apt-get install -y --no-install-recommends \\" >> Dockerfile
- echo "at-spi2-core build-essential desktop-file-utils ffmpeg ghostscript git glib-networking gobject-introspection graphviz-dev gtk-doc-tools hicolor-icon-theme intltool iso-codes libappstream-glib-dev libbz2-dev libdbus-glib-1-dev libexif-dev libgexiv2-dev libgirepository1.0-dev libgtk-3-bin libgtk-3-dev libgudev-1.0-dev libjson-glib-dev liblcms2-dev liblzma-dev libmng-dev libmypaint-dev libopenexr-dev libpoppler-glib-dev libraw-dev libraw19 librsvg2-dev libspiro-dev libsuitesparse-dev libtiff-dev libtiff5-dev libtool libumfpack5 libwebp-dev libwmf-dev libxmu-dev libxpm-dev luajit meson mypaint-brushes poppler-data python3 valac xauth xvfb" >> Dockerfile
- /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --destination $CI_REGISTRY_IMAGE:build-debian-latest --cache=true --cache-ttl=120h
build-image-win64:
stage: prepare
variables:
GIT_STRATEGY: none
cache: {}
image:
name: gcr.io/kaniko-project/executor:debug
entrypoint: [""]
script:
- mkdir -p /kaniko/.docker
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
- echo "FROM debian:testing" > Dockerfile
- echo "RUN apt-get update" >> Dockerfile
- echo "RUN apt-get install -y --no-install-recommends \\" >> Dockerfile
- echo "build-essential cpio g++-mingw-w64-x86-64 gcc-mingw-w64-x86-64 git intltool libgdk-pixbuf2.0-dev libglib2.0-bin meson pkg-config python3 python3-distutils python3-docutils python3-pip rpm xsltproc" >> Dockerfile
- /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --destination $CI_REGISTRY_IMAGE:build-win64-latest --cache=true --cache-ttl=120h
build-image-win32:
stage: prepare
variables:
GIT_STRATEGY: none
cache: {}
image:
name: gcr.io/kaniko-project/executor:debug
entrypoint: [""]
script:
- mkdir -p /kaniko/.docker
- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
- echo "FROM debian:testing" > Dockerfile
- echo "RUN apt-get update" >> Dockerfile
- echo "RUN apt-get install -y --no-install-recommends \\" >> Dockerfile
- echo "build-essential cpio g++-mingw-w64-i686 gcc-mingw-w64-i686 git intltool libgdk-pixbuf2.0-dev libglib2.0-bin meson pkg-config python3 python3-distutils python3-docutils python3-pip rpm xsltproc" >> Dockerfile
- /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --destination $CI_REGISTRY_IMAGE:build-win32-latest --cache=true --cache-ttl=120h
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
## GNU/Linux 64-bit CIs (Debian testing) ##
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
deps-debian:
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
stage: dependencies
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
image: $CI_REGISTRY_IMAGE:build-debian-latest
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
cache:
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
paths:
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
- apt-cache
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
artifacts:
.gitlab-ci.yml: change artifact expiry to 2 hours for dependencies and 1 day for MS Windows builds
2020-05-04 00:29:43 +08:00
expire_in: 2 hours
gitlab-ci: improve artifacts settings. First replace the "when: on_failure" rule by a "when: always". We indeed always want to get log artifact so that we can study a build if necessary (neither only on failure nor on success; really on all cases, since even an apparently successful build may have issues we might want to diagnose). Also expire all artifacts at 1 week (it seems the default on GNOME's Gitlab is 4 weeks; we don't need to keep these so long. Even a few days might be enough actually). As for the artifacts contents, keep the build dirs rather than the install dirs. Build dirs allow to check configuration logs and other kind of logs which are the most useful when diagnosing a failed build. Now install dirs are also interesting. Maybe we should provide them again at some point. We'll see. For now I comment them out. Still keep the install dir for dependencies though, since it seems this is how data are passed from one job to another. Note that ideally we would like to provide different artifacts depending on failure or success but apparently this is currently not possible. See: https://gitlab.com/gitlab-org/gitlab/issues/18744 Also not sure why for GIMP, the CI was only keeping the build app/tests/ directory. We should really keep the whole dir.
2019-10-02 00:36:07 +08:00
when: always
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
paths:
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
- "${INSTALL_DIR}"
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
- _babl/_build
gitlab-ci: improve artifacts settings. First replace the "when: on_failure" rule by a "when: always". We indeed always want to get log artifact so that we can study a build if necessary (neither only on failure nor on success; really on all cases, since even an apparently successful build may have issues we might want to diagnose). Also expire all artifacts at 1 week (it seems the default on GNOME's Gitlab is 4 weeks; we don't need to keep these so long. Even a few days might be enough actually). As for the artifacts contents, keep the build dirs rather than the install dirs. Build dirs allow to check configuration logs and other kind of logs which are the most useful when diagnosing a failed build. Now install dirs are also interesting. Maybe we should provide them again at some point. We'll see. For now I comment them out. Still keep the install dir for dependencies though, since it seems this is how data are passed from one job to another. Note that ideally we would like to provide different artifacts depending on failure or success but apparently this is currently not possible. See: https://gitlab.com/gitlab-org/gitlab/issues/18744 Also not sure why for GIMP, the CI was only keeping the build app/tests/ directory. We should really keep the whole dir.
2019-10-02 00:36:07 +08:00
- _gegl/_build
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
before_script:
gitlab-ci: port our main CI to Debian testing. The old custom ArchLinux got broken (apparently by some package signature verification which fails, and obviously we don't want to bypass these for security reasons). I took the opportunity to port to Debian testing because this is GIMP's base distribution for support (basically dependency versions must be in Debian testing) so it makes sense that our CI is based off it as well. Note though that I am not against additional CI tests so if someone absolutely wants to get the Archlinux-based CI back and thinks it gets us some additional worthy test, feel free to fix whatever was broken then we may add it back (having both Debian testing and Archlinux CI).
2020-01-02 02:57:06 +08:00
- git clone --depth=${GIT_DEPTH} https://gitlab.gnome.org/GNOME/babl.git _babl
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
- git clone --depth=${GIT_DEPTH} https://gitlab.gnome.org/GNOME/gegl.git _gegl
gitlab-ci: port our main CI to Debian testing. The old custom ArchLinux got broken (apparently by some package signature verification which fails, and obviously we don't want to bypass these for security reasons). I took the opportunity to port to Debian testing because this is GIMP's base distribution for support (basically dependency versions must be in Debian testing) so it makes sense that our CI is based off it as well. Note though that I am not against additional CI tests so if someone absolutely wants to get the Archlinux-based CI back and thinks it gets us some additional worthy test, feel free to fix whatever was broken then we may add it back (having both Debian testing and Archlinux CI).
2020-01-02 02:57:06 +08:00
- export PKG_CONFIG_PATH="${INSTALL_PREFIX}/lib/pkgconfig"
- export PKG_CONFIG_PATH="${INSTALL_PREFIX}/lib/`gcc -print-multiarch`/pkgconfig/:$PKG_CONFIG_PATH"
- export LD_LIBRARY_PATH="${INSTALL_PREFIX}/lib:${LD_LIBRARY_PATH}"
- export LD_LIBRARY_PATH="${INSTALL_PREFIX}/lib/`gcc -print-multiarch`:$LD_LIBRARY_PATH"
- export XDG_DATA_DIRS="${INSTALL_PREFIX}/share:/usr/local/share:/usr/share"
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
script:
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
- cd _babl
- meson -Dprefix="${INSTALL_PREFIX}" _build
- ninja -C _build
- ninja -C _build install
- cd ../_gegl
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
- meson --prefix="${INSTALL_PREFIX}" _build
build: .gitlab-ci.yml: GEGL is switching to meson exclusively
2019-08-17 03:30:57 +08:00
- ninja -C _build
- ninja -C _build install
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
needs: ["build-image"]
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
.gimp-debian-base:
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
stage: gimp
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
image: $CI_REGISTRY_IMAGE:build-debian-latest
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
dependencies:
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
- deps-debian
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
cache:
paths:
- apt-cache
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
artifacts:
.gitlab-ci.yml: expire all dependencies in 2 hours, and all builds in 1 day
2020-05-09 19:19:18 +08:00
expire_in: 1 days
gitlab-ci: improve artifacts settings. First replace the "when: on_failure" rule by a "when: always". We indeed always want to get log artifact so that we can study a build if necessary (neither only on failure nor on success; really on all cases, since even an apparently successful build may have issues we might want to diagnose). Also expire all artifacts at 1 week (it seems the default on GNOME's Gitlab is 4 weeks; we don't need to keep these so long. Even a few days might be enough actually). As for the artifacts contents, keep the build dirs rather than the install dirs. Build dirs allow to check configuration logs and other kind of logs which are the most useful when diagnosing a failed build. Now install dirs are also interesting. Maybe we should provide them again at some point. We'll see. For now I comment them out. Still keep the install dir for dependencies though, since it seems this is how data are passed from one job to another. Note that ideally we would like to provide different artifacts depending on failure or success but apparently this is currently not possible. See: https://gitlab.com/gitlab-org/gitlab/issues/18744 Also not sure why for GIMP, the CI was only keeping the build app/tests/ directory. We should really keep the whole dir.
2019-10-02 00:36:07 +08:00
when: always
name: "app-build-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
paths:
gitlab-ci: improve artifacts settings. First replace the "when: on_failure" rule by a "when: always". We indeed always want to get log artifact so that we can study a build if necessary (neither only on failure nor on success; really on all cases, since even an apparently successful build may have issues we might want to diagnose). Also expire all artifacts at 1 week (it seems the default on GNOME's Gitlab is 4 weeks; we don't need to keep these so long. Even a few days might be enough actually). As for the artifacts contents, keep the build dirs rather than the install dirs. Build dirs allow to check configuration logs and other kind of logs which are the most useful when diagnosing a failed build. Now install dirs are also interesting. Maybe we should provide them again at some point. We'll see. For now I comment them out. Still keep the install dir for dependencies though, since it seems this is how data are passed from one job to another. Note that ideally we would like to provide different artifacts depending on failure or success but apparently this is currently not possible. See: https://gitlab.com/gitlab-org/gitlab/issues/18744 Also not sure why for GIMP, the CI was only keeping the build app/tests/ directory. We should really keep the whole dir.
2019-10-02 00:36:07 +08:00
- _build
#- "${INSTALL_DIR}"
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
before_script:
gitlab-ci: port our main CI to Debian testing. The old custom ArchLinux got broken (apparently by some package signature verification which fails, and obviously we don't want to bypass these for security reasons). I took the opportunity to port to Debian testing because this is GIMP's base distribution for support (basically dependency versions must be in Debian testing) so it makes sense that our CI is based off it as well. Note though that I am not against additional CI tests so if someone absolutely wants to get the Archlinux-based CI back and thinks it gets us some additional worthy test, feel free to fix whatever was broken then we may add it back (having both Debian testing and Archlinux CI).
2020-01-02 02:57:06 +08:00
- export PKG_CONFIG_PATH="${INSTALL_PREFIX}/lib/pkgconfig:${INSTALL_PREFIX}/share/pkgconfig"
- export PKG_CONFIG_PATH="${INSTALL_PREFIX}/lib/`gcc -print-multiarch`/pkgconfig/:$PKG_CONFIG_PATH"
- export PKG_CONFIG_PATH="${INSTALL_PREFIX}/share/`gcc -print-multiarch`/pkgconfig/:$PKG_CONFIG_PATH"
- export LD_LIBRARY_PATH="${INSTALL_PREFIX}/lib:${LD_LIBRARY_PATH}"
- export LD_LIBRARY_PATH="${INSTALL_PREFIX}/lib/`gcc -print-multiarch`:$LD_LIBRARY_PATH"
- export XDG_DATA_DIRS="${INSTALL_PREFIX}/share:/usr/local/share:/usr/share"
- export PATH="${INSTALL_PREFIX}/bin:$PATH"
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
needs: ["deps-debian"]
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
gimp-autotools-debian:
extends: .gimp-debian-base
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
script:
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
- mkdir _build
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
- cd _build
gitlab-ci: our CI base system (Arch) fixed their libmypaint package. See: https://bugs.archlinux.org/task/62468
2019-09-11 23:09:05 +08:00
- ../autogen.sh
refactoring of the gitlab-ci.yml
2019-08-21 19:54:38 +08:00
--prefix="${INSTALL_PREFIX}"
--enable-debug
--with-python=force
--with-javascript=force
--with-lua=force
- make -j "$(nproc)"
gitlab-ci: enabling make check on master CI. Also install missing xauth (required by xvfb-run). `make check` was broken on CI, but got fixed by commits 707d3c6f64, f6e9c6ee6f, 2c1efdedf0 and of course the present one.
2020-03-18 02:43:27 +08:00
- make check
build: adding a .gitlab-ci.yml file for automated GitLab pipeline builds
2019-07-29 07:11:44 +08:00
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
gimp-distcheck-debian:
extends: .gimp-debian-base
gitlab-ci: add a distcheck step on master too. Similar to the distcheck step only contributed by schumaml on gimp-2-10.
2020-08-03 08:27:29 +08:00
script:
- mkdir _build
- cd _build
- ../autogen.sh
--prefix="${INSTALL_PREFIX}"
--enable-debug
--with-python=force
--with-javascript=force
--with-lua=force
--enable-gtk-doc
- make -j "$(nproc)"
gitlab-ci: run distcheck with multi-jobs.
2020-08-07 21:30:05 +08:00
- make -j "$(nproc)" distcheck
gitlab-ci: add a distcheck step on master too. Similar to the distcheck step only contributed by schumaml on gimp-2-10.
2020-08-03 08:27:29 +08:00
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
gimp-meson-debian:
extends: .gimp-debian-base
Update gitlab-ci
2019-08-09 22:18:43 +08:00
script:
- meson _build
--prefix="${INSTALL_PREFIX}"
-Dpython=always
-Djavascript=always
-Dlua=always
- ninja -C _build
gitlab-ci: run unit tests for meson builds. Not because they are working better than the ones in autotools, but rather because it seems they are simply barely implemented! So of course, the few tests currently there work.
2020-01-04 05:55:09 +08:00
- ninja -C _build test
Update gitlab-ci
2019-08-09 22:18:43 +08:00
gitlab-ci: rename the CI jobs. The Linux CI job names are too long and are not recognizable on the web GUI unless you hover the widgets with the mouse to read tooltips. Remove the "/testing" part (if people want to know exactly which Debian we use for our builds, they can always look at the script) and move left the differenciating parts (i.e. autotools/meson/clang/distcheck) so that these are visible in a glance, even when ellipsing long job names.
2020-08-06 19:21:05 +08:00
gimp-clang-debian:
extends: .gimp-debian-base
gitlab-ci: test a CLang build.
2020-01-03 07:19:10 +08:00
variables:
CC: "clang"
CXX: "clang++"
script:
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
- mkdir -p "$APT_CACHE"
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
- apt-get install -y --no-install-recommends -o dir::cache::archives="$APT_CACHE"
gitlab-ci: fix recently broken CLang compilation. Fixes: > /usr/bin/ld: cannot find -lomp
2020-03-16 05:21:19 +08:00
clang libomp-dev
gitlab-ci: test a CLang build.
2020-01-03 07:19:10 +08:00
- meson _build
--prefix="${INSTALL_PREFIX}"
-Dpython=always
-Djavascript=always
-Dlua=always
- ninja -C _build
gitlab-ci: run unit tests for meson builds. Not because they are working better than the ones in autotools, but rather because it seems they are simply barely implemented! So of course, the few tests currently there work.
2020-01-04 05:55:09 +08:00
- ninja -C _build test
gitlab-ci: test a CLang build.
2020-01-03 07:19:10 +08:00
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
## WINDOWS 64-bit CI ##
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
deps-win64:
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
stage: dependencies
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
image: $CI_REGISTRY_IMAGE:build-win64-latest
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
variables:
XDG_CACHE_HOME: "$CI_PROJECT_DIR/.cache/"
XDG_DATA_HOME: "$CI_PROJECT_DIR/.local/share/"
cache:
paths:
- .cache/crossroad/
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
- apt-cache
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
before_script:
build: use msys2 packages as source for the Windows CI. This is a new feature I implemented in the crossroad cross-compilation tool. Msys2 repository has more packages and they are more up-to-date compared to Fedora and Suse cross-built packages (the 2 other available sources for pre-built Windows packages). This allows to simplify a lot the dependency preparation for the Windows CI, and speed things up.
2020-04-16 21:19:36 +08:00
- git clone --depth=${GIT_DEPTH} git://git.tuxfamily.org/gitroot/crossroad/crossroad.git
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
- cd crossroad
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
- ./setup.py install --prefix=`pwd`/../.local
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
- cd ..
gitlab-ci: fix Windows CI builds. Seems that msys2 packages can sometimes be compressed as `.tar.zst` instead of `.tar.xz`. I updated crossroad to handle this case. It now requires the additional pypi `zstandard` package.
2020-04-27 20:46:11 +08:00
- pip3 install zstandard
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
script:
- export PATH="`pwd`/.local/bin:$PATH"
gitlab-ci, build: add a wrapper for GIMP binary to Win32 CI result. A few commands need to be performed the first time for glib to work properly, and gdk-pixbuf loaders to be found. I add them in a wrapper script so that it's easy to ask people to test the dev builds (even though it's not necessary to run these commands each time, but who cares!).
2019-10-25 04:20:20 +08:00
- crossroad w64 gimp --run="build/windows/crossbuild-gitlab-ci/build-deps.sh"
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
artifacts:
name: "${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
.gitlab-ci.yml: change artifact expiry to 2 hours for dependencies and 1 day for MS Windows builds
2020-05-04 00:29:43 +08:00
expire_in: 2 hours
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
paths:
- .local/
- _deps/
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
needs: ["build-image-win64"]
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
gimp-win64:
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
stage: gimp
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
image: $CI_REGISTRY_IMAGE:build-win64-latest
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
dependencies:
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
- deps-win64
gitlab-ci: fix crossroad and dnf caching. This should hopefully speed up successive builds as most packages don't need to be re-downloaded.
2019-10-01 19:44:42 +08:00
variables:
XDG_CACHE_HOME: "$CI_PROJECT_DIR/.cache/"
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
XDG_DATA_HOME: "$CI_PROJECT_DIR/.local/share/"
gitlab-ci: fix crossroad and dnf caching. This should hopefully speed up successive builds as most packages don't need to be re-downloaded.
2019-10-01 19:44:42 +08:00
cache:
paths:
- .cache/crossroad/
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
- apt-cache
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
script:
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
- export PATH="`pwd`/.local/bin:$PATH"
- mkdir _build && cd _build
- echo 'crossroad meson ..
build: use msys2 packages as source for the Windows CI. This is a new feature I implemented in the crossroad cross-compilation tool. Msys2 repository has more packages and they are more up-to-date compared to Fedora and Suse cross-built packages (the 2 other available sources for pre-built Windows packages). This allows to simplify a lot the dependency preparation for the Windows CI, and speed things up.
2020-04-16 21:19:36 +08:00
-Dgtk-doc=false
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
-Dpython=always -Dlua=always
gitlab-ci: no need to specify explicitly -Dbuildtype=debugoptimized. This has now been changed to be the default meson build by Ell in the previous commit.
2019-10-26 19:00:46 +08:00
-Djavascript=always && ninja install &&
gitlab-ci: move the prefix to root for simpler paths in artefacts.
2019-10-25 04:47:56 +08:00
cp ../build/windows/crossbuild-gitlab-ci/gimp-wrapper.cmd $CROSSROAD_PREFIX/bin/ &&
cp -fr $CROSSROAD_PREFIX/ ../gimp-prefix/
gitlab-ci, build: add a wrapper for GIMP binary to Win32 CI result. A few commands need to be performed the first time for glib to work properly, and gdk-pixbuf loaders to be found. I add them in a wrapper script so that it's easy to ask people to test the dev builds (even though it's not necessary to run these commands each time, but who cares!).
2019-10-25 04:20:20 +08:00
' |
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
crossroad w64 gimp --run="-"
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
needs: ["deps-win64"]
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
artifacts:
gitlab-ci: new build organization. Rather than having the whole Win32 cross-build into the 'gimp' stage, break the dependencies and GIMP-only builds in 2 stages. Since apparently we need to keep the same structure for the native and cross build (otherwise we don't get parallel builds; in other words, I didn't find the possibility to set separate pipelines up), I move babl and GEGL into the same 'dependencies' stage. Finally I remove the -base rules extended into actual jobs, except for `.gimp-base` (this is the only which makes sense as it is actually common to the meson and autotools build).
2019-10-02 03:36:19 +08:00
name: "${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
gitlab-ci: improve artifacts settings. First replace the "when: on_failure" rule by a "when: always". We indeed always want to get log artifact so that we can study a build if necessary (neither only on failure nor on success; really on all cases, since even an apparently successful build may have issues we might want to diagnose). Also expire all artifacts at 1 week (it seems the default on GNOME's Gitlab is 4 weeks; we don't need to keep these so long. Even a few days might be enough actually). As for the artifacts contents, keep the build dirs rather than the install dirs. Build dirs allow to check configuration logs and other kind of logs which are the most useful when diagnosing a failed build. Now install dirs are also interesting. Maybe we should provide them again at some point. We'll see. For now I comment them out. Still keep the install dir for dependencies though, since it seems this is how data are passed from one job to another. Note that ideally we would like to provide different artifacts depending on failure or success but apparently this is currently not possible. See: https://gitlab.com/gitlab-org/gitlab/issues/18744 Also not sure why for GIMP, the CI was only keeping the build app/tests/ directory. We should really keep the whole dir.
2019-10-02 00:36:07 +08:00
when: always
.gitlab-ci.yml: expire all dependencies in 2 hours, and all builds in 1 day
2020-05-09 19:19:18 +08:00
expire_in: 1 day
build, gitlab-ci: add a script to cross-build GIMP with Gitlab CI. It looks like Arch does not have mingw64 cross-compilers in core package repository. It does have some package in the user repository (AUR), but I assume that such a repository cannot be deemed as safe. Anyway I still tried, but apparently these AUR packages have to be built and when I tried, I got this error: > ERROR: Running makepkg as root is not allowed as it can cause > permanent, catastrophic damage to your system. Anyway it's all a big mess. Then I tried to move the cross-CI to Debian testing, which is anyway our base compatibility system. Unfortunately I encountered like what looked like some glibc++ macro problem on some packages (most likely because the pre-built packages I use are Fedora ones which likely uses a cross-compiler differently built from the Debian one). So in the end, for simplicity, I use a Fedora image, then I am sure to get a good match between the system cross-compiler and the pre-built dependencies.
2019-09-25 20:27:09 +08:00
paths:
- _build/
gitlab-ci: move the prefix to root for simpler paths in artefacts.
2019-10-25 04:47:56 +08:00
- gimp-prefix/
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
## WINDOWS 32-bit CI ##
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
deps-win32:
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
stage: dependencies
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
image: $CI_REGISTRY_IMAGE:build-win32-latest
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
variables:
XDG_CACHE_HOME: "$CI_PROJECT_DIR/.cache/"
XDG_DATA_HOME: "$CI_PROJECT_DIR/.local/share/"
cache:
paths:
- .cache/crossroad/
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
- apt-cache
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
before_script:
build: use msys2 packages as source for the Windows CI. This is a new feature I implemented in the crossroad cross-compilation tool. Msys2 repository has more packages and they are more up-to-date compared to Fedora and Suse cross-built packages (the 2 other available sources for pre-built Windows packages). This allows to simplify a lot the dependency preparation for the Windows CI, and speed things up.
2020-04-16 21:19:36 +08:00
- git clone --depth=${GIT_DEPTH} git://git.tuxfamily.org/gitroot/crossroad/crossroad.git
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
- cd crossroad
- ./setup.py install --prefix=`pwd`/../.local
- cd ..
gitlab-ci: fix Windows CI builds. Seems that msys2 packages can sometimes be compressed as `.tar.zst` instead of `.tar.xz`. I updated crossroad to handle this case. It now requires the additional pypi `zstandard` package.
2020-04-27 20:46:11 +08:00
- pip3 install zstandard
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
script:
- export PATH="`pwd`/.local/bin:$PATH"
- crossroad w32 gimp --run="build/windows/crossbuild-gitlab-ci/build-deps.sh"
artifacts:
name: "${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
.gitlab-ci.yml: expire all dependencies in 2 hours, and all builds in 1 day
2020-05-09 19:19:18 +08:00
expire_in: 2 hours
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
paths:
- .local/
- _deps/
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
needs: ["build-image-win32"]
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
gimp-win32:
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
stage: gimp
CI: use custom docker images for dependencies and GIMP builds
2020-05-30 06:41:22 +08:00
image: $CI_REGISTRY_IMAGE:build-win32-latest
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
dependencies:
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
- deps-win32
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
variables:
XDG_CACHE_HOME: "$CI_PROJECT_DIR/.cache/"
XDG_DATA_HOME: "$CI_PROJECT_DIR/.local/share/"
cache:
paths:
- .cache/crossroad/
app: CI cache now configured in GNOME gitlab. Let's reimplement some caching of packages for Debian apt and crossroad. Hopefully it should speed up subsequent builds.
2020-05-29 01:51:50 +08:00
- apt-cache
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
script:
- export PATH="`pwd`/.local/bin:$PATH"
- mkdir _build && cd _build
- echo 'crossroad meson ..
-Dwmf=disabled -Dgtk-doc=false
-Dpython=always -Dlua=always
-Djavascript=always && ninja install &&
cp ../build/windows/crossbuild-gitlab-ci/gimp-wrapper.cmd $CROSSROAD_PREFIX/bin/ &&
cp -fr $CROSSROAD_PREFIX/ ../gimp-prefix/
' |
crossroad w32 gimp --run="-"
gitlab-ci: job renaming.
2019-11-26 02:16:40 +08:00
needs: ["deps-win32"]
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
artifacts:
name: "${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
when: always
.gitlab-ci.yml: change artifact expiry to 2 hours for dependencies and 1 day for MS Windows builds
2020-05-04 00:29:43 +08:00
expire_in: 1 day
gitlab-ci: add a Windows 32-bit CI. Some issues may happen only for 32-bit builds. So it may be worth make a Windows 32-bit build too. Issue #2794 triggered this reasonning, though in this issue's case, simply the build would not have discovered the bug since it was only a build warning + run-time bug. Still long-term if we manage to get a no-warning build, it could become relevant to discover more errors at build time. So preparing the ground work here.
2019-11-25 02:41:06 +08:00
paths:
- _build/
- gimp-prefix/
gitlab-ci: add an analysis stage with cppcheck code analysis stage. As contributed by Rafał @qarmin in a Gitlab comment. See #5002.
2020-04-29 00:39:32 +08:00
cppcheck:
stage: analysis
before_script:
- apt-get update
- apt-get install -y cppcheck
script:
gitlab-ci: ignore a bunch of directories. Problem with the CI is that the source is straight in our base directory and therefore installed dependency files as well as cache or built files are in subfolders. Let's try to ignore as much as I can see. This should avoid a bunch of warning and errors during report generation.
2020-04-29 20:05:31 +08:00
- cppcheck -q -j8 --enable=all --force --output-file=cppcheck.xml --xml --xml-version=2
-i _build -i _deps -i gimp-prefix -i .local -i .cache .
gitlab-ci: add an analysis stage with cppcheck code analysis stage. As contributed by Rafał @qarmin in a Gitlab comment. See #5002.
2020-04-29 00:39:32 +08:00
- mkdir report
- cppcheck-htmlreport --source-dir=. --title=gimp --file=cppcheck.xml --report-dir=report
artifacts:
name: "${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
expire_in: 1 week
when: always
paths:
- report
gitlab-ci: cppcheck does not need to wait for previous stages to occur.
2020-05-05 22:21:43 +08:00
needs: []
gitlab-ci: add a distribution step. I don't add this at the end of the distcheck job to make the interface clearer, and also because the distcheck job will have full build artifacts (allowing to debug a failing distcheck if necessary), whereas the `sources` job will just publish tarballs and SHA256 sums generated from these tarballs. Simple, clean.
2020-08-07 22:41:05 +08:00
## Ready-to-distribute ##
sources:
stage: distribution
dependencies:
- gimp-distcheck-debian
artifacts:
when: always
paths:
- gimp-*.tar.*
- SHA256SUMS
script:
- mv _build/gimp-*.tar.* .
- sha256sum gimp-*.tar.* > SHA256SUMS
needs: ["gimp-distcheck-debian"]