bundles/craft/README.md

0001 Craft CI/CD Repositories
0002 ------------------------
0003
0004 KDE uses a common framework named Craft based on Python to process applications
0005 continuous workflow on different platforms:
0006
0007 - Continuous Integration (CI - Build Factory).
0008 - Continuous Deployement (CD - Binary Factory).
0009
0010 The workflow supports notarization of application bundles (signing) for Linux (AppImage and Snap), Windows, and MacOS stores.
0011
0012 * Documentations and tutorials:
0013
0014 - Front page                    : https://community.kde.org/Craft
0015 - Settings details              : https://community.kde.org/Craft/Blueprints
0016 - Introduction to binary factory: https://kfunk.org/2017/11/17/kde-binary-factory/
0017
0018 * Git repositories:
0019
0020 - KF dependencies used by Craft : https://invent.kde.org/sysadmin/repo-metadata/-/tree/master/dependencies
0021 - Craft core implementation     : https://invent.kde.org/packaging/craft
0022 - Configuration                 : https://invent.kde.org/packaging/craft-blueprints-kde/-/tree/master/extragear/digikam
0023 - Binary factory customizations : https://invent.kde.org/sysadmin/binary-factory-tooling/-/blob/master/craft/enabled-projects.yaml
0024
0025 * Jenkins Web interfaces:
0026
0027 - Build Factory Jenkins page    : https://build.kde.org/
0028 - Binary Factory Jenkins page   : https://binary-factory.kde.org/
0029
0030 Notes:
0031
0032 - All changes performed to Binary Factory customizations files needs a DSL Job to be triggered by KDE sysadmin team.
0033   This job will synchronize the settings to the Binary Factory environnements.
0034
0035 - Changes from Binary Factory customizations allow to specify which version of dependencies must by installed to compile digiKam.
0036   For each dependency versions installed, the same release must be specified in build factory configuration.
0037
0038 - The Craft Core python repository host all low level implementation and rules to use in Craft BluePrints configurations.