CI Utilisation and system efficiency

[Vlad Zahorodnii]

On 4/19/25 10:53 AM, Kai Uwe Broulik wrote:
> Hi,
>
> thanks for looking into this.
>
> It seems a major contributor to CI time is the fact that a merge 
> request runs and once merged, master runs another pretty much 
> identical pipeline right after that.
>
> As for KWin: Not sure which one we could axe. KWin uses a bunch of 
> internal Qt stuff, so catching Qt dev regressions/private API changes 
> early is important.

Not sure what we can do about kwin. I looked how we can reduce the time 
needed to run tests, and there's not much space for improvements 
anymore. Speaking for kwin, I personally wouldn't mind if KDE adopts a 
different policy regarding running CI. For example, only run CI when 
it's time to merge a change and after a change lands in master or if a 
pipeline is manually triggered by a developer.

Regards,
Vlad