Skip to content

New cron.* maintenance to cleanup action job/run/task tables #25923

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nicorac opened this issue Jul 17, 2023 · 1 comment
Closed

New cron.* maintenance to cleanup action job/run/task tables #25923

nicorac opened this issue Jul 17, 2023 · 1 comment
Labels
issue/duplicate The issue has already been reported. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@nicorac
Copy link

nicorac commented Jul 17, 2023

Feature Description

I'm testing the new Gitea Actions feature (I know, it's still a preview, but it works great for me...) and I've filled up Actions log with hundreds of (now useless) test runs.
I see there's no way to cleanup them other than straight access to DB.

The existing cron.delete_old_actions only deletes repo user actions (like pushes, issue close, ...) but does not cleanup the CI/CD Actions log.

Should be great to have a new maintenance job to cleanup actions_job, actions_run and action_task tables as like as the existing cron.delete_old_actions maintenance task cleans up the actions table.

I think there's no need to keep that history forever, at least in small & personal Gitea instances.

An alternative could be to extend the existing cron.delete_old_actions task to cleanup those tables too, maybe with different run parameters.

@nicorac nicorac added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jul 17, 2023
@wolfogre
Copy link
Member

I think it's duplicated with #24256.

@wolfogre wolfogre added the issue/duplicate The issue has already been reported. label Jul 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants