Our great sponsors
-
Looks like the issue is tracked in https://gitlab.com/gitlab-org/gitlab/-/issues/368326
Example of a public project with negative project storage: https://gitlab.com/strivinglife/book-raspberry-pi
-
Git LFS is a pretty widely accepted stack for managing binary blobs by reference in git: https://git-lfs.github.com/
The plugin is installed out of the box in many git distributions now. Many hosts support it today, including Gitlab, which is relevant to this article's discussion: https://docs.gitlab.com/ee/topics/git/lfs/
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
bfg-repo-cleaner
Removes large or troublesome blobs like git-filter-branch does, but faster. And written in Scala
> erhaps now is a good time to recommend the ever-popular BFG to anyone unaware: https://rtyley.github.io/bfg-repo-cleaner/
Thanks for sharing this tool to help cleanup the Git history. Please be aware that it will rewrite the history, which could be very impactful to existing branches, merge requests and local clones. A similar approach is described in the documentation: https://docs.gitlab.com/ee/user/project/repository/reducing_...
-
My Qt/C++ cross-platform FOSS Wallpaper Engine project[1] currently uses 47gb of storage. This is because I compile for every platform and store the artifacts for 4 weeks. Not sure what I will do in the future, because having older builds around to try out without recompiling is always nice.
-
Also, for some things there is no retention policy configurable at all -- eg pipelines and their associated stdout logs appear to not be auto-cleaned-up at any expiry date (no default, nothing configurable). If you want to get rid of those you need to script it via the API, it seems: eg https://gitlab.com/eskultety/gitlab_cleaner
(I just ran that on the QEMU project and reduced the usage from 295GB to 165GB by deleting pipelines older than 1 Jan... so that's a lot of low-hanging logfile fruit gitlab could be auto-deleting.)
-
Looks like the issue is tracked in https://gitlab.com/gitlab-org/gitlab/-/issues/368326
Example of a public project with negative project storage: https://gitlab.com/strivinglife/book-raspberry-pi
-
DefinitelyTyped:
$ git clone https://github.com/DefinitelyTyped/DefinitelyTyped
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Home Assistant
:house_with_garden: Open source home automation that puts local control and privacy first.
home-assistant/core:
$ git clone https://github.com/home-assistant/core
-
-
Thanks for the suggestion of adding a Git cache for a GitLab Runner. A similar mechanism already exists that allows control of the Git strategy with fetch on a local working copy which is faster, and clone if not yet existing. All benefits and limitations are documented [0].
To help prevent unneeded traffic when a new pipeline job is executed, GitLab Runner uses a shallow Git clone by default on GitLab.com SaaS that only pulls a limited set of Git commits from the current head instead of a full clone. [1]
There is a feature proposal [2] to add support for partial clone and sparse-checkout strategies that have been added in more recent Git versions. Recommend commenting/subscribing.
Please note that for GitLab.com SaaS Shared Runners, the traffic limits do not apply with mostly internal cloud traffic. [3]
[0] https://docs.gitlab.com/ee/ci/runners/configure_runners.html...
[1] https://docs.gitlab.com/ee/ci/large_repositories/#shallow-cl...
[2] https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26631
[3] https://about.gitlab.com/pricing/#what-counts-towards-my-tra...