Laurent Trinques 4d3f20f79a CI: build the Linux AppImage with the Windows CI/CD and list it on the nightly page ...

Add .github/workflows/linux-appimage.yml, a reusable workflow that runs
the build-aux/linux/appimage scripts on an ubuntu-24.04 runner (same
glibc 2.39 as the reference build host) and publishes the AppImage and
its SHA256 file on the nightly-qt6 release.

It has no trigger of its own: windows-msi.yml calls it in parallel with
build-msi, with the same condition, so the AppImage is only built when
the Windows CI/CD runs. deploy-pages now waits for both jobs; its
condition still only looks at build-msi, so an AppImage failure never
blocks the Windows part of the page.

- Qt (aqtinstall) and the static KDE Frameworks are kept in the Actions
  cache, keyed by QT_VERSION and KF_VERSION: only QET is built per run.
- Checkout without LFS (issue #975) and with full history (revision
  number of the AppImage name).
- The previous AppImage is only deleted from the release once a new one
  has been built, as for the MSI.

Scripts:
- QET_SOURCE_DIR builds an existing checkout instead of cloning QET.
- No dist-upgrade on CI runners; aqt install skipped when Qt is cached.
- RELEASEID.txt/GITCOMMIT.txt are written in the work directory, so
  moving or replacing the scripts directory no longer breaks 03.
- appimage.readme: new CONTINUOUS INTEGRATION section.

generate-page.py: optional Linux section (APPIMAGE_URL, APPIMAGE_NAME),
with the file name shown, since after a failed AppImage build the
previous one stays on the release. Header now "Nightly Builds".

2026-10-25 16:49:09 +01:00

..

workflows

CI: build the Linux AppImage with the Windows CI/CD and list it on the nightly page

2026-10-25 16:49:09 +01:00