Optimize disk usage by deleting successful build logs after 7 days.
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
(CC @ryanaslett)
At the moment, Jenkins stores build logs for 21 days (both successes and failures). Given the number of CIs executed daily, this leads to a huge volume of logs.
Since successful build logs don’t offer much valuable insight, how about reducing their retention period to just 7 days?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Jenkins configuration that controls build-log retention and review how successful and failed builds are currently handled. Done means successful build logs are retained for 7 days while failed-build logs remain available for 21 days, with the configuration updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100