Re: Transition to VM based CI

urrently provisioning new nodes is significantly labour intensive as well (see https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-templates/README.md for the instructions). This is essentially completely eliminated with the transition to VM

Re: Transition to VM based CI

On Montag, 7. Juli 2025 18:17:37 Mitteleuropäische Sommerzeit Milian Wolff wrote: > Are the base VM images built using Ansible or something and thus available > to interested developers too as a means to get quickly into a dev setup? > Especially for Windows that would be great to have, but it wou

Re: Transition to VM based CI

e actions >> that have all previously been restricted by operating in a container >> environment. >> >> The system will also generally benefit from being able to scale build >> capacity for different OSes on an as needed basis within our available >> hardware (so

Re:  Transition to VM based CI

ed by hand and disk space allocated between > them in a fixed fashion. This means that any cleanup from stale disk > images, over-filled caches, etc. has to be done 3 times on each build node > (being the Linux host as well as the FreeBSD and Windows guest VMs). > Currently provisioning new n

Re: Transition to VM based CI

ently provisioning new nodes is significantly labour intensive as > well > > (see > > > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-templates/ > > README.md for the instructions). > > > > This is essentially completely eliminated with the transition t

Re: Transition to VM based CI

e FreeBSD and Windows guest VMs). > Currently provisioning new nodes is significantly labour intensive as well > (see > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-templates/ > README.md for the instructions). > > This is essentially completely eliminated wit

Re: Transition to VM based CI

is essentially completely eliminated with the transition to VM based CI, with the majority of the deployment now being possible using Ansible with the only manual step being the registration with Gitlab - which is a fairly quick process taking less than 20 minutes per node. Maintenance is significan

Transition to VM based CI

the transition to VM based CI, with the majority of the deployment now being possible using Ansible with the only manual step being the registration with Gitlab - which is a fairly quick process taking less than 20 minutes per node. Maintenance is significantly reduced as each node only needs one

Re: Upcoming CI changes - transition to VM based CI

On Thu, Jun 12, 2025 at 12:22 AM Luigi Toscano wrote: > Ben Cooksley ha scritto: > > On Wed, Jun 11, 2025 at 8:56 PM Albert Astals Cid > > wrote: > > > > El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa > > central), Ben Cooksley va escriure: >

Re: Upcoming CI changes - transition to VM based CI

Ben Cooksley ha scritto: > On Wed, Jun 11, 2025 at 8:56 PM Albert Astals Cid > wrote: > > El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > > > My concern is that if we keep pushing out terminating sup

Re: Upcoming CI changes - transition to VM based CI

On Wed, Jun 11, 2025 at 8:56 PM Albert Astals Cid wrote: > El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa > central), Ben Cooksley va escriure: > > > > My concern is that if we keep pushing out terminating support those > > > > projects will just keep deferring their portin

Re: Upcoming CI changes - transition to VM based CI

El dimarts, 10 de juny del 2025, a les 9:31:55 (Hora d’estiu d’Europa central), Ben Cooksley va escriure: > > > My concern is that if we keep pushing out terminating support those > > > projects will just keep deferring their porting. > > > Note that Frameworks 6 released in Feb 2024, so they've h

Re: Upcoming CI changes - transition to VM based CI

gt; > > > > > checks > > > > > > and > > > > > > website builds, and is not intended for running general CI/CD > > > > > > builds. > > > > > > > > > > > > The tooling used by the CI nodes

Re: Upcoming CI changes - transition to VM based CI

t; wish > > > > > > > > > to run any of those images (say for FreeBSD or Android), although > > > > > you > > > > > > > > will > > > > > > > > > need to setup libvirt yourself (SUSE has very good instructions for >

Re: Upcoming CI changes - transition to VM based CI

uctions for > > > > this, > > > > Debian less so as their instructions lack installing the packages > needed > > > > > > to > > > > > > > provide UEFI and TPM support). The tooling itself was merged this > > > >

Re: Upcoming CI changes - transition to VM based CI

On Tuesday, 3 June 2025 11:42:08 CEST Ben Cooksley wrote: > For FreeBSD the story is much the same as SUSE - packages are being removed > as apps upgrade to Qt 6 and the Qt 5 version of libraries becomes surplus > to requirements. >From the FreeBSD packaging side, we have zero interest in Qt5 for

Re: Upcoming CI changes - transition to VM based CI

folder) and can be used with the VM > > > images found at https://storage.kde.org/vm-images/ > > > > > > There is however one downside to this - Qt 5 support. > > > > > > Over the past few months distributions have been steadily removing > > >

Re: Upcoming CI changes - transition to VM based CI

ding anything else, it will not be > possible for us to produce Qt 5 based VM build images for any of the 3 > platforms. > > We will therefore have to remove Qt 5 support from the CI system with the > transition to VM based CI. From previous discussio

Re: Upcoming CI changes - transition to VM based CI

On Montag, 2. Juni 2025 16:42:01 Mitteleuropäische Sommerzeit Christoph Cullmann wrote: > Have we some overview how many things on invent.kde.org will loose the the > CI as they are still Qt 5 only? Looking at things that still have Qt5 jobs in the CI, it's a pretty mixed bag: * Plugins needed to

Re: Upcoming CI changes - transition to VM based CI

On 2025-06-02, Ben Cooksley wrote: > As launching VMs is not the most efficient approach for all workloads, > limited support for running Docker containers will be preserved, however > this support is primarily intended for running linters, sanity checks and > website builds, and is not intended f

Re: Upcoming CI changes - transition to VM based CI

On Tue, Jun 3, 2025 at 10:32 PM Sune Vuorela wrote: > On 2025-06-02, Ben Cooksley wrote: > > As launching VMs is not the most efficient approach for all workloads, > > limited support for running Docker containers will be preserved, however > > this support is primarily intended for running lint

Re: Upcoming CI changes - transition to VM based CI

On Tue, Jun 3, 2025 at 11:23 PM Sune Vuorela wrote: > On 2025-06-03, Ben Cooksley wrote: > > Not sure why we're wanting to monitor for compilation on an Ubuntu LTS > > specifically, would have thought that was something best watched by our > > Appimage CD builds. Those are currently performed on

Re: Upcoming CI changes - transition to VM based CI

On 2025-06-03, Ben Cooksley wrote: > Not sure why we're wanting to monitor for compilation on an Ubuntu LTS > specifically, would have thought that was something best watched by our > Appimage CD builds. Those are currently performed on a SLES image. The purpose is to test that one can do applica

Re: Upcoming CI changes - transition to VM based CI

been steadily removing > packages > > and other supporting infrastructure needed to keep Qt 5 builds alive. In > > the case of Windows, support for the entire Qt 5 tree has been > unmaintained > > for some time. For FreeBSD and SUSE a significant number of packages have >

Re: Upcoming CI changes - transition to VM based CI

ntained for some time. For FreeBSD and SUSE a significant number of > > packages have been removed - which in the case of SUSE also includes > > packages needed to support the building of KJS. Accordingly, because > > builds of Frameworks are a first stepping stone to support building &

Re: Upcoming CI changes - transition to VM based CI

first stepping stone to support building anything else, it will not be > possible for us to produce Qt 5 based VM build images for any of the 3 > platforms. > > We will therefore have to remove Qt 5 support from the CI system with the > transition to VM based CI. From previous

Re: Upcoming CI changes - transition to VM based CI

packages and other supporting infrastructure needed to keep Qt 5 builds > alive. In the case of Windows, support for the entire Qt 5 tree has been > unmaintained for some time. For FreeBSD and SUSE a significant number of > packages have been removed - which in the case of SUSE also includes >

Re: Upcoming CI changes - transition to VM based CI

Am Montag, 2. Juni 2025, 16:42:01 Mitteleuropäische Sommerzeit schrieb Christoph Cullmann: > On Monday, June 2nd, 2025 at 13:40, Ben Cooksley wrote: > > We will therefore have to remove Qt 5 support from the CI system with the > > transition to VM based CI. > > > >

invent.k.o/games (Re: Upcoming CI changes - transition to VM based CI)

Am Montag, 2. Juni 2025, 17:06:15 Mitteleuropäische Sommerzeit schrieb Benson Muite: > Can also help with some of the Games software. I can speed you (and others) up with looking at the games (at least those in invent.kde.org/games): There is one unreleased which needs related work: Kolorfill,

Re: Upcoming CI changes - transition to VM based CI

ting infrastructure needed to keep Qt 5 builds alive. In the >> case of Windows, support for the entire Qt 5 tree has been unmaintained for >> some time. For FreeBSD and SUSE a significant number of packages have been >> removed - which in the case of SUSE also includes packages n

Re: Upcoming CI changes - transition to VM based CI

gt; There is however one downside to this - Qt 5 support. > >> > > > >> Over the past few months distributions have been steadily removing > >> packages and other supporting infrastructure needed to keep Qt 5 builds > >> alive. In the case of Windows, supp

Re: Upcoming CI changes - transition to VM based CI

rst > stepping stone to support building anything else, it will not be possible for > us to produce Qt 5 based VM build images for any of the 3 platforms. > > We will therefore have to remove Qt 5 support from the CI system with the > transition to VM based CI. > > Please let me know if there are any questions on the above. Have we some overview how many things on invent.kde.org will loose the the CI as they are still Qt 5 only? Greetings Christoph signature.asc Description: OpenPGP digital signature

Upcoming CI changes - transition to VM based CI

efore have to remove Qt 5 support from the CI system with the transition to VM based CI. Please let me know if there are any questions on the above. Thanks, Ben