The console logs on gallium are a bit large. Jenkins knows how to read from them when they are compressed using gzip.
Under /var/lib/jenkins/jobs/ we should find any file named "log" which is more than a day old and gzip -9 them.
Description
Description
Details
Details
- Reference
- bz63939
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Declined | Krinkle | T65939 Write a cronjob to compress old Jenkins builds' logs |
Event Timeline
Comment Actions
Change 125991 had a related patch set uploaded by Hashar:
contint: compress Jenkins console logs once per day
Comment Actions
Change 125991 abandoned by Hashar:
contint: compress Jenkins console logs once per day
Reason:
Abandoning the change. The find command takes 5 hours to traverse the hierarchy and compress a few files. Meanwhile, that cause high CPU and I/O on the gallium server which has a bunch of interesting side effects such as: Jenkins dieing, jobs timeout etc.
Instead of compressing. I will just kill the job history after a few months.
Comment Actions
Per Antoine, let's instead use Jenkins' built-in mechanism to purge old builds in general. Thus removing them entirely instead of compressing.
Comment Actions
I have installed Jenkins Compress Build Log Plugin which at least get the console output logs compressed :)