CI Utilisation and system efficiency

[Martin Gysel]

Am Samstag, 19. April 2025, 10:33:45 Mitteleuropäische Sommerzeit schrieb Ben Cooksley:
> > 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.
> 
> Gitlab doesn't support what you are describing i'm afraid - there is no way
> of telling it "i'm ready to merge this change now".
> Realistically merge requests shouldn't be proposed until people are ready
> to get something reviewed and merged in...

there is, mark the merge request as draft. it's possible to skip pipelines for draft merge 
requests:
https://docs.gitlab.com/ci/yaml/workflow/#skip-pipelines-for-draft-merge-requests[1]


/martin


--------
[1] https://docs.gitlab.com/ci/yaml/workflow/#skip-pipelines-for-draft-merge-requests
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20250419/34a4ef4d/attachment.htm>