CI Utilisation and system efficiency

[Ben Cooksley]

On Sun, Apr 20, 2025 at 3:19 AM Akseli Lahtinen <akselmo at akselmo.dev> wrote:

> On Friday 18 April 2025 22:25:36 Eastern European Summer Time Ben Cooksley
> wrote:
> > Hi all,
> >
> > Over the past week or two there have been a number of complaints
> regarding
> > CI builder availability which i've done some investigating into this
> > morning.
> >
>
> Hi, is there a possibility we don't run CI for every commit?
> I tend to make many commits in merge requests, when iterating over
> something. I use commits very much as save states,
> deleting/reverting/amending
> them a lot.


> I've noticed that a CI runs for *every* commit I do, even amends and such.
> I don't think there's really need to do it so often. Instead, would it
> make
> more sense to run CI only when the merge request is going to be merged?


CI doesn't run for every commit - it runs on the top commit for each push
you make.

By amends are you referring to the apply suggestion feature?
If so, i'd suggest using the batching function so you can put all the
suggestions into one commit (see
https://docs.gitlab.com/user/project/merge_requests/reviews/suggestions/#batch-suggestions
)


>
>
> Br,
> - Akseli
>
>
>
Cheers,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20250420/71f927ad/attachment-0001.htm>