CI Utilisation and system efficiency

Ben Cooksley bcooksley at kde.org
Sat Apr 19 21:34:21 BST 2025


On Sun, Apr 20, 2025 at 3:05 AM Thomas Friedrichsmeier <
thomas.friedrichsmeier at kdemail.net> wrote:

> On Sat, 19 Apr 2025 07:25:36 +1200
> Ben Cooksley <bcooksley at kde.org> wrote:
> [...]
> > This morning I ran a basic query to ascertain the top 20 projects for
> > CI time utilisation on invent.kde.org which revealed the following:
>
> What (rough) percentage is that of the total? I.e. is the problem more
> one of a few projects hogging up most resources, or is it waste across
> the board? (Also keeping in mind that using a lot of resources may also
> be a sign of a lot of development activity).
>
> For RKWard, I believe it's our deployment jobs that take up a
> disproportionate amount of time (and I have tossed out one of those,
> now). Personally, I would be quite happy, if those would run with some
> delay (possibly with an option to trigger them early, manually). No
> idea, whether a change like that would make a noticeable difference, if
> applied across the board.
>

I've had a look and Gitlab supports delaying the start of jobs.
See https://docs.gitlab.com/ci/jobs/job_control/#run-a-job-after-a-delay


>
> Regards
> Thomas
>

Cheers,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20250420/8dd4de67/attachment.htm>


More information about the kde-devel mailing list