Speakers
Description
From compiling, automated testing, linting and license verification over producing application packages for various platforms to shipping signed production releases to app stores, KDE's CI/CD system offers many ways to support you in developing software and getting it to your users.
Biography
Ben became involved in KDE over 15 years ago and has over this time contributed to KDE software, websites and for some time now, played an active role in maintaining the infrastructure that supports KDE.org and services operating on it.
When Hannah had this one problem 14 years ago and joined the #KDE-Windows IRC channel, little did she know how this would change her life. She now maintains KDE Craft for more than 10 years and transformed the former Windows only build tool to a cross-platform CI/CD package manager. Which is capable of producing fully standalone deployments for Linux, Windows and Mac.
Julius started his journey with KDE about 5 years ago at Kdenlive. Over the past years he also contributed to KDE Craft, Flatpak and the CI/CD infrastructure, where the transitions from Qt5 to Qt6 and from Jenkins to GitLab were some of the major task.
Volker joined KDE more than 20 years ago and has since contributed to KDE Frameworks, KDE PIM and Akonadi, ELF Dissector, the digital travel assistance app KDE Itinerary and three major version transitions of KDE's software stack.
Description
With the migration from Jenkins to Gitlab which was concluded earlier this year, the CI/CD infrastructure not only gained new capabilities but also became more accessible for contributors to set up and customize things. In this talk, we will give an overview of the available features and how to best employ those for your application.
We will cover continuous integration (CI), that is compiling, testing and linting changes as they appear in Git or in merge requests, on all supported platforms as well as continuous delivery (CD), that is producing ready-made runnable/installable application packages in various formats, for testing individual changes or for production releases to app stores.
Finally we'll also look at current developments and future plans.
