added a section about how to adjust the CI for projects using Flatpak
CI (scroll a bit under the minimal example).
Hi,
this is CMake, not meson, there is no ‘meson-dist’ directory under the
flatpak build directory here. Back at the square 1, I need the git
command here. I noticed the ‘tarball’ stage runs with
Using Docker executor with image Quay
I tried to switch to the “quay.io/gnome_infrastructure/gnome-runtime-
images:gnome-master”, which the flatpak stage uses, and it does have
the git command, thus it’s a bit better. It still fails, just with a
different error:
$ git archive --prefix=${TARBALL_PATH_PREFIX}/ HEAD | xz -z > ${TARBALL_NAME}
fatal: detected dubious ownership in repository at '/builds/mcrha/evolution-data-server'
To add an exception for this directory, call:
git config --global --add safe.directory /builds/mcrha/evolution-data-server
Looking what it is, the files are extracted as root:root, with one
build:build file:
$ ls -la
total 8928
drwxrwxrwx. 1 root root 548 Dec 27 09:14 .
drwxrwxrwx. 1 root root 92 Dec 27 09:14 ..
-rw-rw-rw-. 1 root root 210 Dec 27 09:14 .dir-locals.el
-rw-rw-rw-. 1 root root 195 Dec 27 09:14 .editorconfig
drwxrwxrwx. 1 root root 10 Dec 27 09:14 .flatpak-builder
drwxrwxrwx. 1 root root 86 Dec 27 09:14 .git
-rw-rw-rw-. 1 root root 33 Dec 27 09:14 .gitignore
-rw-rw-rw-. 1 root root 3060 Dec 27 09:14 .gitlab-ci.yml
-rw-rw-rw-. 1 root root 0 Dec 27 09:14 AUTHORS
-rw-rw-rw-. 1 root root 36621 Dec 27 09:14 CMakeLists.txt
-rw-rw-rw-. 1 root root 25290 Dec 27 09:14 COPYING
-rw-rw-rw-. 1 root root 366 Dec 27 09:14 ChangeLog
-rw-rw-rw-. 1 root root 0 Dec 27 09:14 HACKING
-rw-rw-rw-. 1 root root 30 Dec 27 09:14 MAINTAINERS
-rw-rw-rw-. 1 root root 479821 Dec 27 09:14 NEWS
-rw-rw-rw-. 1 root root 655 Dec 27 09:14 README
drwxrwxrwx. 1 root root 136 Dec 27 09:14 cmake
-rw-rw-rw-. 1 root root 6631 Dec 27 09:14 config.h.in
drwxrwxrwx. 1 root root 3990 Dec 27 09:14 data
drwxrwxrwx. 1 root root 540 Dec 27 09:14 docs
-rw-r--r--. 1 build build 8537944 Dec 27 09:06 evolution-data-server-nightly.flatpak
-rw-rw-rw-. 1 root root 1112 Dec 27 09:14 evolution-data-server.doap
-rw-rw-rw-. 1 root root 655 Dec 27 09:14 evolution-data-server.pc.in
-rw-rw-rw-. 1 root root 5910 Dec 27 09:14 iconv-detect.c
drwxrwxrwx. 1 root root 1134 Dec 27 09:14 po
drwxrwxrwx. 1 root root 236 Dec 27 09:14 src
drwxrwxrwx. 1 root root 232 Dec 27 09:14 tests
Following the hint from the git command failure (see above), it makes
the tarball. This tarball seems to be a correct tarball.
One last thing, is there an easy way to verify the ${CI_COMMIT_TAG}
contains an expected data, aka in this case:
? Creating the tarball for other tags is useless.
By the way, may not be the tarballs marked with anything like
expire_in: 14 days
in the CI? There is no need to keep them ad infinity in the CI, I
guess.
I also verified a failed ‘tarball’ job with a tag is restarted with the
proper CI_COMMIT_TAG variable set. That’s fine.
The Release notes seem to use the Tag commit message.
I’m not going to copy the NEWS file changes into the tag, not talking
the “Tag 1.2.3 release” is useless for the release notes. Maybe it’s
only for the sandbox though.
I guess I have the things ready now. Thanks for the guides and patience
with me. We’ll see whether I really made it right soon. It did take far
more than 10 minutes advertised by Emmanuele
(GNOME Release Service - ftpadmin replacement - Coming 11th December - #6 by ebassi
GNOME Release Service - ftpadmin replacement - Coming 11th December - #6 by ebassi)
), but I guess it’s due to the differences between me and him.
Bye,
Milan