Please welcome a new way to build Geany and Geany-Plugins for Windows in the CI.

What's in here:

the workflow job to checkout Geany-Plugins, Geany and Infrastructure repositories
use the supporting scripts in https://github.com/geany/infrastructure/tree/add_ci_builders/builders to
- build a Docker image with a full MSYS2 installation (or pull the image from the Geany Docker registry if available)
- use this Docker image to:
  - build Geany and create a release-like installer for it as build dependency for the G-P build (or use cache if available)
  - install Geany from the previously built Geany installer
  - build Geany-Plugins and create and test an installer
  - store the Geany and Geany-Plugins installer as artifact on Github

Mostly all of the work is done in the builder scripts on https://github.com/geany/infrastructure/tree/add_ci_builders/builders.
Unfortunately, it grew more than than expected in terms of amount of code.

I tried to document at least the basics so anyone else than me will be available to get an idea what is happening.
Let me know if it worked :).

There is a difference to the Linux CI build which more or less aims at using a rather old setup to ensure backwards compability.
The Mingw-w64 build instead always pulls the latest available packages from the MSYS2 repositories.
I think this is OK as this is also what we do on releases and since we bundle all dependencies into the installer (for release builds as well as for CI builds), the result should be consistent.

Best of all: during the CI build Windows installers are created for Geany and Geany-Plugins and they are stored as artifacts and can be downloaded later on (up to 30 days).

TODO:

this branch needs a bit more testing with this PR
we need to merge the PR XXX first
for now, the necessary Docker image was uploaded to https://github.com/geany/infrastructure/pkgs/container/geany-mingw64-ci by me manually. Basically we could push the image also from the CI job but I'm hesitating to allow this because of the risks it offers to malicious users. Maybe I'll add a separate job in the infrastructure repository later to build and push the image there and restrict this job to admins

You can view, comment on, or merge this pull request online at:

https://github.com/geany/geany-plugins/pull/1201

Commit Summary

10d401e CI: Add Windows build
da2bf88 CI: Add Windows build
cf09e20 CI: Add Windows build
ced0a1a CI: Add Windows build
3fdffd7 CI: Add Windows build
3a8ecbb CI: Add Windows build
a95a8c1 CI: Add Windows build
f10ddda CI: Add Windows build
0bf5ef9 CI: Add Windows build
5ed0637 CI: Add Windows build
b85195c CI: Add Windows build
a99a9c3 CI: Add Windows build
495b8b6 CI: Add Windows build
d90629c CI: Add Windows build
8f403fa CI: Add Windows build
bdb2b36 CI: Add Windows build
3f6b6b6 CI: Add Windows build
0b31bee CI: Add Windows build
f9bcc29 CI: Add Windows build
c5c0413 CI: Add Windows build
9f5e54b CI: Add Windows build
69febe0 CI: Add Windows build
377bd4e CI: Add Windows build
5c9fc36 CI: Add Windows build
246672c CI: Add Windows build
9d3ffa9 CI: Add Windows build
62bed3d CI: Add Windows build
ff5745b CI: Add Windows build
1809f8e CI: Add Windows build
ba4b041 CI: Add Windows build
c28a4c3 CI: Add Windows build
c7a46c0 CI: Add Windows build
8c07a76 CI: Add Windows build
f0e3dfe CI: Add Windows build
0da53cb CI: Add Windows build
38196e1 CI: Add Windows build
c0ec040 Fix g-p source path
f099253 CI: Add Windows build
8cfd770 CI: Add Windows build
ba62a3e CI: Add Windows build

File Changes

(1 file)

M .github/workflows/build.yml (140)

Patch Links:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.