NkwaTambe opened a new pull request, #5922:
URL: https://github.com/apache/fineract/pull/5922
## Problem
The fineract repo is responsible for **$102.02** of the org GitHub billing
this month, despite being a public repo with free compute minutes. The cost
comes from **storage overages** (artifacts + container images) exceeding the
org free tier.
Current state: **21,697 artifacts** accumulated, with retention of 5-30
days, across 15 workflow files.
## Changes
### 1. Reduce artifact retention-days from 5/7/30 to 1 day
- 29 occurrences across 15 workflow files changed to `retention-days: 1`
- Artifacts auto-delete after 1 day instead of hoarding for weeks
### 2. Add concurrency groups to prevent duplicate runs
- `full-build-ci.yml`: adds concurrency group `ci-${{ github.ref }}` with
`cancel-in-progress: true`
- `publish-ghcr.yml`: adds concurrency group `publish-ghcr-${{ github.ref
}}` with `cancel-in-progress: true`
- Cancels older in-progress runs when a new push arrives on the same branch,
preventing wasted storage from redundant runs
## Impact
- **Immediate**: New artifacts expire after 1 day instead of 5-30 days
- **Prevents duplicate runs**: Concurrency groups cancel redundant CI runs
on same branch
- **No functional impact**: All workflow jobs remain identical; only
retention timing and run deduplication changed
## Remaining manual cleanup needed
1. **Delete existing old artifacts** — 17,670+ artifacts still in storage
(API rate-limited during cleanup, needs org admin or GitHub Support to
bulk-purge)
2. **Delete old container image versions** from GHCR (fineract,
fineract/sms-gateway, fineract/fineract-config-cli, etc.)
3. **Set org-wide spending limit** to prevent future surprises
4. **Consider reducing Docker publish frequency** — currently publishes on
every push to develop
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
