Upcoming CI changes - transition to VM based CI

[Ben Cooksley]

On Tue, Jun 3, 2025 at 10:32 PM Sune Vuorela <nospam at vuorela.dk> wrote:

> On 2025-06-02, Ben Cooksley <bcooksley at kde.org> 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 for running general CI/CD builds.
>
> Okular has compile jobs for testing some minimal baselines of supported
> systems. I don't know if Okular is the only one, but I at least think it
> is a great idea that we have these kind of jobs also.
>
> (We want people to be able to build Okular preferably on Ubuntu LTS or
> later distributions, but due to the timing of last Ubuntu LTS and the
> release of KF6, we currently have it on a 'more modern' ubuntu )
>
> Okular also have a custom clazy & clang-tidy jobs that relies on
> python3 -u ci-utilities/run-ci-build.py to provision a setup.


> I'm unsure which of these will have to be re-done, discarded or anything
> else in this setup.
>

Please note that custom jobs while permitted on our CI are something that
the project developers are responsible for supporting.

I've taken a quick look and can confirm that build_clazy_clang_tidy won't
need any changes - it should automatically carry over without any issues
and will run in a VM build without changes being required because it
inherits from one of the sysadmin provided jobs.
clang_format would be covered as a linter job so that should also be fine
in theory. build_ubuntu_24_10 will likely be fine, as long as it is not too
resource intensive then it should not have any issues.

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.


> /Sune
>
>
Thanks,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20250603/1e233897/attachment.htm>