3 ms·

We're affected by this change, and have been trying to get support in forums, but can't get hold of anyone. Build Artifacts are listed as part of what contribu

We're affected by this change, and have been trying to get support in forums, but can't get hold of anyone. Build Artifacts are listed as part of what contributes to the quota (which is fair enough), but there's no way (that I could find in the docs) to manage build artifacts that are stored. I suspect we have a large historic storage, which we don't use / need, but there's no way to browse this, no way to verify it, and no way to delete what we don't need. I'm dreading getting a big ole bill in a few months for storage we had no way to opt out of.

xiaq 4y ago
I have a repo that was almost exactly 5GB and it turned out that the storage was also used exclusively by pipeline logs and artifacts. Found this recipe on StackOverflow to just nuke everything and worked for me: https://stackoverflow.com/questions/71513286/clean-up-history-in-gitlab-pipeline https://stackoverflow.com/questions/71513286/clean-up-histor.... You can tweak it a bit if you want to keep the more recent pipeline runs. For some reason I had to run this multiple times to completely remove everything; each run removes about half of all the pipelines and only when there were about 20 remaining did the script remove everything.
lbotos 4y ago
GitLab Support Engineering Manager here. These limits will first be soft limits as they are now. Impacted users will be notified and there will be about 2 months to take action before enforcement starts. After that point, limits will be enforced. If you’d like to investigate now you can use the GitLab API to fetch job artifacts and their storage size: https://docs.gitlab.com/ee/api/jobs.html#list-project-jobs https://docs.gitlab.com/ee/api/jobs.html#list-project-jobs and calculate the summary. I’d suggest collecting all pipeline jobs to be deleted using this API endpoint https://docs.gitlab.com/ee/api/job_artifacts.html#delete-job-artifacts https://docs.gitlab.com/ee/api/job_artifacts.html#delete-job... We are looking to improve the visibility for job artifacts in the UI as we get nearer to the storage limit being enforced.
- deleted 4y ago
  [deleted]

xiaq 4y ago

I have a repo that was almost exactly 5GB and it turned out that the storage was also used exclusively by pipeline logs and artifacts. Found this recipe on StackOverflow to just nuke everything and worked for me: https://stackoverflow.com/questions/71513286/clean-up-history-in-gitlab-pipeline https://stackoverflow.com/questions/71513286/clean-up-histor.... You can tweak it a bit if you want to keep the more recent pipeline runs. For some reason I had to run this multiple times to completely remove everything; each run removes about half of all the pipelines and only when there were about 20 remaining did the script remove everything.

lbotos 4y ago

GitLab Support Engineering Manager here. These limits will first be soft limits as they are now. Impacted users will be notified and there will be about 2 months to take action before enforcement starts. After that point, limits will be enforced. If you’d like to investigate now you can use the GitLab API to fetch job artifacts and their storage size: https://docs.gitlab.com/ee/api/jobs.html#list-project-jobs https://docs.gitlab.com/ee/api/jobs.html#list-project-jobs and calculate the summary. I’d suggest collecting all pipeline jobs to be deleted using this API endpoint https://docs.gitlab.com/ee/api/job_artifacts.html#delete-job-artifacts https://docs.gitlab.com/ee/api/job_artifacts.html#delete-job... We are looking to improve the visibility for job artifacts in the UI as we get nearer to the storage limit being enforced.

deleted 4y ago
[deleted]