[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Please cleanup old forks
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2024-04-20 23:16:22
Message-ID: CA+XidOEfYCuwtNDf9S+L3D3QwNF_3xU_Cww_wS4qJ84NQQWCxw () mail ! gmail ! com
[Download RAW message or body]

Hi all,

As part of routine maintenance on Invent (Gitlab) i've been reviewing the
total amount of space currently being consumed by repositories.

At this time, the top 100 largest repositories on Invent (we have 14,000 or
so for context) are consuming around 21% of the total space. It would
therefore be good if we could please clean this up.

To add a bit of context, we currently have around 140GB of repositories,
and a further 30GB of pooled repository data (shared among the canonical
repository and it's forks). Those top 100 repositories currently use 30GB
of space - so as much as all of the pools.

Forks of KDevelop and docs-krita-org feature heavily on the list of large
repositories.

Of particular interest are old forks (created more than 2-3 years ago) as
these are often not participating in Gitlab's mechanism to reduce the disk
space taken by forks (known as pool repositories).

As an additional note: please do not fork a fork, as these forks-of-forks
cannot participate in a pool and must carry a full copy of the upstream
repository data. If you have a situation where a network of forks of forks
has developed please consider options to resolve this.

I know Krita at least has this situation presently with their fork of
various parts of Qt that is being maintained in people's personal
namespaces.

Thanks,
Ben

[Attachment #3 (text/html)]

<div dir="ltr">Hi all,<div><br></div><div>As part of routine maintenance on Invent \
(Gitlab) i&#39;ve been reviewing the total amount of space currently being consumed \
by repositories.  </div><div><br></div><div>At this time, the top 100 largest \
repositories on Invent (we have 14,000 or so for context) are consuming around 21% of \
the total space. It would therefore be good if we could please clean this \
up.</div><div><br></div><div>To add a bit of context, we currently have around 140GB \
of repositories, and a further 30GB of pooled repository data (shared among the \
canonical repository and it&#39;s forks). Those top 100 repositories currently use \
30GB of space - so as much as all of the pools.</div><div><br></div><div><div>Forks \
of KDevelop and docs-krita-org feature heavily on the list of large \
repositories.</div></div><div><br></div><div>Of particular interest are old forks \
(created more than 2-3 years ago) as these are often not participating in \
Gitlab&#39;s  mechanism to reduce the disk space taken by forks (known as pool \
repositories).  </div><div><br></div><div>As an additional note: please do not fork a \
fork, as these forks-of-forks cannot participate in a pool and must carry a full copy \
of the upstream repository data. If you have a situation where a network of forks of \
forks has developed please consider options to resolve \
this.</div><div><br></div><div>I know Krita at least has this situation presently \
with their fork of various parts of Qt that is being maintained in people&#39;s \
personal namespaces.</div><div><br></div><div>Thanks,</div><div>Ben</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]