Skip to content

binary-factory.kde.org migration to the Gitlab CI

Tracker task for migration of <binary-factory.kde.org> to the Gitlab CI. Similar to the #9 (closed) but for binary-factory. I have tried to put tasks in various phases which does not need to finished in order.

Website builds

One of super easy items to migrate to Gitlab CI, there's templates for most of the binary-factory.kde.org items already at https://invent.kde.org/sysadmin/ci-tooling/-/tree/master/invent , see websites-*.yml files.

  • Go through various templates for websites
  • Register a secure runner which have a rsync access to the nicoda.kde.org for uploading artifacts
  • Enable the specific runner for the websites / documentation projects which have templates
  • Disable jobs from binary-factory

Android builds

  • Add template for android builds, check : ci-tooling!70 (closed)
  • Add job for signing of the android builds
  • Register a secure runner which allows the access to the keystore and can do signing
  • Lock down the projects using the specific runner by specifying the template ci config

Flatpak jobs

  • Potentially dissolve the flatpak-kde-applications and move specific flatpak recipes to their own repos
  • Check the template of the flatpak build jobs and modify it to export repository instead of bundle
  • Add job for signing of the flatpak repository
  • Lock down projects using specific signer runner by specifying template ci config

Appimage builds

This builds seems to be super custom and I think each will require the job configuration for each repository

Windows builds

Todo: document

MacOS builds

Todo: document

Snap builds

Todo: document

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information