Managing Actions storage space

On https://github.com/organizations/my-org/settings/billing I can see that our organization is using 2.5 GBs (out of which 2 would be free). I also see these warnings:

> You’ve used 100% of included services for GitHub Storage (GitHub Actions and Packages)

> GitHub Actions and Packages won’t work until a monthly spending limit is set.

Nevertheless, Actions still fully works.

It is not clear what counts towards this usage, what this restriction will affect and how to mitigate it.

We extensively use caching and artifacts features. I’m assuming that either or both count towards the limit. We especially have large (~100MB) artifacts for a certain job (my guess for the culprit). This would result in an infinitely growing storage size.

I have a few observations / possibly feature requests:

  • I don’t see a way to delete artifacts, nor would I want to do it manually. Having old artifacts which don’t fit the quota removed automatically is reasonable, as it is being done for the cache feature (“The total size of all caches in a repository don’t exceed 2 GB. If you exceed this limit, GitHub will save your cache but will begin evicting caches until the total size is less than 2 GB.”).

  • I think features recycling storage space (e.g. cache) should not count towards the limit, or the sum of them should fit well within the limit. For example, if I currently use the cache feature and it counts towards the limit it can just fill up automatically and I won’t be able to use other features.

  • If artifacts were to be recycled, I would like to be able to keep some of them indefinitely (understandably these would count towards the limit). For example, I would be OK with recycling dev build artifacts but not release build artifacts.

  • For recycled items, I would like to be able to set a custom limit per repository. Since the limit is shared within the organization and some repositories may use it more extensively than others it’s possible that a single project takes up all of the limit. I would like to avoid this.

11 Likes

After reaching out to support I got the following response:

At this time, artifacts are deleted automatically on a rolling 90-day basis. Our team is working to add the ability to delete artifacts, but with the holidays approaching it will likely be January before that feature is available. The initial rollout will likely be a very basic version that leaves room for iteration to perhaps allow customization at a later point.

5 Likes

It is now possible to delete artifacts manually.

To delete artifacts, visit a build and click on the Artifacts link in the upper right. If you have write access to the repo, you should see red trashcan icons to remove any artifacts you no longer need.

3 Likes

Do you know if there is a setting to change this value?

“Visit a build”? What is meant by this? The term build isn’t really used anywhere in GitHubs vocabulary. 

Do you mean the result of a GitHub Action job? Or a built package in the Packages repo? In either case, I don’t see anything related to artifacts or removal. 

Our team has created an Action to periodically clean up old artifacts:

https://github.com/c-hive/gha-remove-artifacts

It also supports keeping tagged (release) artifacts.

6 Likes

There isn’t one at the moment but we created an action to solve this, see the accepted solution: https://github.community/t5/GitHub-Actions/Managing-Actions-storage-space/m-p/51291#M8134

Actions -> Select a run in the list -> Select a job on the left side

You end up at e.g. https://github.com/org/repo/runs/533166375

In the upper-right corner, you will see an Artifacts menu. After clicking you will see the artifacts and can delete them as well.

Screenshot from 2020-03-25 13-34-36.png

Hey! What do you mean by old artifacts? The one before the previous builds artifacts and releases right?