Manage actions cache in Gitea #11424

New Issue

GiteaMirror · 2025-11-02T09:37:15-06:00

GiteaMirror commented

2025-11-02 09:37:15 -06:00

Originally created by @RecordingTheSmile on GitHub (Aug 9, 2023).

Feature Description

We can now utilize caching in all Actions through actions/cache. However, Gitea still lacks caching management functionality, meaning it's not possible to view current cache keys or delete caches within Gitea.

It would be great if Gitea could implement a cache management feature similar to what is available on GitHub.

Screenshots

No response

Originally created by @RecordingTheSmile on GitHub (Aug 9, 2023). ### Feature Description We can now utilize caching in all Actions through `actions/cache`. However, Gitea still lacks caching management functionality, meaning it's not possible to view current cache keys or delete caches within Gitea. It would be great if Gitea could implement a cache management feature similar to what is available on GitHub. ### Screenshots _No response_

GiteaMirror added the topic/gitea-actions type/proposal labels 2025-11-02 09:37:15 -06:00

GiteaMirror commented

2025-11-02 09:37:15 -06:00

@VAllens commented on GitHub (Jan 19, 2024):

+10000000000000000000000

@VAllens commented on GitHub (Jan 19, 2024): +10000000000000000000000

GiteaMirror commented

2025-11-02 09:37:16 -06:00

@sebthom commented on GitHub (Jan 22, 2024):

I think the issue is not only about cache management via the UI. It seems like there is currently also no way to programmatically delete caches. In GHA I can delete a cache in a build step like this: https://docs.github.com/en/rest/actions/cache?apiVersion=2022-11-28#delete-github-actions-caches-for-a-repository-using-a-cache-key but looking at the Swagger API of Gitea there is no equivalent.

@sebthom commented on GitHub (Jan 22, 2024): I think the issue is not only about cache management via the UI. It seems like there is currently also no way to programmatically delete caches. In GHA I can delete a cache in a build step like this: https://docs.github.com/en/rest/actions/cache?apiVersion=2022-11-28#delete-github-actions-caches-for-a-repository-using-a-cache-key but looking at the Swagger API of Gitea there is no equivalent.

GiteaMirror commented

2025-11-02 09:37:16 -06:00

@RecordingTheSmile commented on GitHub (Jan 30, 2024):

I think the issue is not only about cache management via the UI. It seems like there is currently also no way to programmatically delete caches. In GHA I can delete a cache in a build step like this: https://docs.github.com/en/rest/actions/cache?apiVersion=2022-11-28#delete-github-actions-caches-for-a-repository-using-a-cache-key but looking at the Swagger API of Gitea there is no equivalent.

Agree. And Gitea uses local data storage library instead of common C/S database (like MySQL), which makes it impossible to remove cache files manually.

@RecordingTheSmile commented on GitHub (Jan 30, 2024): > I think the issue is not only about cache management via the UI. It seems like there is currently also no way to programmatically delete caches. In GHA I can delete a cache in a build step like this: https://docs.github.com/en/rest/actions/cache?apiVersion=2022-11-28#delete-github-actions-caches-for-a-repository-using-a-cache-key but looking at the Swagger API of Gitea there is no equivalent. Agree. And Gitea uses local data storage library instead of common C/S database (like MySQL), which makes it impossible to remove cache files manually.

GiteaMirror commented

2025-11-02 09:37:16 -06:00

@lunny commented on GitHub (Jan 30, 2024):

I think the issue is not only about cache management via the UI. It seems like there is currently also no way to programmatically delete caches. In GHA I can delete a cache in a build step like this: https://docs.github.com/en/rest/actions/cache?apiVersion=2022-11-28#delete-github-actions-caches-for-a-repository-using-a-cache-key but looking at the Swagger API of Gitea there is no equivalent.

Agree. And Gitea uses local data storage library instead of common C/S database (like MySQL), which makes it impossible to remove cache files manually.

We can have a protocl to ask runners to remove the cache.

@lunny commented on GitHub (Jan 30, 2024): > > I think the issue is not only about cache management via the UI. It seems like there is currently also no way to programmatically delete caches. In GHA I can delete a cache in a build step like this: https://docs.github.com/en/rest/actions/cache?apiVersion=2022-11-28#delete-github-actions-caches-for-a-repository-using-a-cache-key but looking at the Swagger API of Gitea there is no equivalent. > > Agree. And Gitea uses local data storage library instead of common C/S database (like MySQL), which makes it impossible to remove cache files manually. We can have a protocl to ask runners to remove the cache.

GiteaMirror commented

2025-11-02 09:37:16 -06:00

@vjm commented on GitHub (Nov 12, 2024):

is there any more information on this? or am i better off using RUNNER_TOOL_CACHE instead?

@vjm commented on GitHub (Nov 12, 2024): is there any more information on this? or am i better off using `RUNNER_TOOL_CACHE` instead?

GiteaMirror commented

2025-11-02 09:37:16 -06:00

@lunny commented on GitHub (Nov 12, 2024):

RUNNER_TOOL_CACHE is different from actions/cache. They are two kinds of cache.

@lunny commented on GitHub (Nov 12, 2024): `RUNNER_TOOL_CACHE` is different from `actions/cache`. They are two kinds of cache.

GiteaMirror commented

2025-11-02 09:37:16 -06:00

@vjm commented on GitHub (Nov 13, 2024):

Yes, correct -- I am not sure that I gain any benefits from actions/cache that I am not able to achieve in the local cache as of now, until actions cache allows for more granular management -- is that right? What would be a good example use case where I should use actions/cache? I am finding that I can use local cache for docker, npm, python, etc...

@vjm commented on GitHub (Nov 13, 2024): Yes, correct -- I am not sure that I gain any benefits from `actions/cache` that I am not able to achieve in the local cache as of now, until actions cache allows for more granular management -- is that right? What would be a good example use case where I should use `actions/cache`? I am finding that I can use local cache for docker, npm, python, etc...

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11424