Automated JFrog Storage Cleanup Reporting
Every Monday, WebRun opens JFrog, reads storage used per repository and how it grew over the week, picks out old artifacts and stale build folders nobody pulls, posts a ranked cleanup list to your platform WhatsApp group, and drafts an approval email in Gmail so a person signs off before anything is removed.
How do I find which artifact repositories are using the most storage?
WebRun reports on JFrog storage every Monday. It reads the space used per repository and its weekly growth, finds old artifacts and build folders nobody pulls, posts a ranked cleanup list to your platform WhatsApp group, and drafts an approval email in Gmail before anything is removed.
- Storage growth is ranked by repository every Monday
- Artifacts still being pulled by builds never reach the cleanup list
- No artifact is deleted without a named owner approving it
Built for platform engineers · DevOps teams · release managers · infrastructure owners
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
jfrog.comin a real browser with your saved login - no setup, no API keys. -
1
JFrog - read storage per repository
WebRun opens JFrog to read storage per repository. - Open JFrog and read the storage used by each repository
- Compare against last week to work out growth per repository
- Identify old artifacts and build folders with no recent downloads, and note which repositories have no retention rule set
Done when Every repository has a size, a weekly growth figure, and a list of reclaimable artifacts.
-
2
WhatsApp - post the ranked cleanup list
WebRun opens WhatsApp to post the ranked cleanup list. - Post the ranked cleanup list to your internal platform group, biggest reclaim first
- Show the repository, its size, its weekly growth, and the space old artifacts would free
- Name the repositories running with no retention rule at all
Done when The platform team has this week's ranked cleanup list in WhatsApp.
-
3
Gmail - draft the approval request
WebRun opens Gmail to draft the approval request. - Draft an approval email to the repository owners listing the artifacts proposed for removal
- Include the repository, the artifact age, the last download date, and the space each item frees
- Leave the email unsent in Gmail drafts. WebRun never deletes an artifact itself
Done when An approval draft is waiting in Gmail for every proposed cleanup.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it delete artifacts on its own?
No. Deletion is never automatic here. WebRun proposes a list and drafts an approval email that stays unsent in Gmail, so a repository owner signs off and removes the artifacts themselves.
How does it decide an artifact is safe to clear?
It looks at age and the last download date against the rules you set, so an old artifact that is still being pulled by a build stays off the list.
Does it change retention rules?
No. It reports which repositories have no retention rule set so you can add one deliberately. WebRun never edits a rule, a permission, or a repository setting.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.