Closed Bug 397979 Opened 17 years ago Closed 16 years ago

manage buildbot logs better

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

Details

qm-rhel02 completely filled up /build tonight with Buildbot logs. This has happened on Build machines in the past, too. We need a way to manage Buildbot logs so this doesn't happen again. AFAIK Buildbot doesn't have any built-in log management. It would be nice if it was capable of deleting logs that were X days old, or a way to tell it "only keep logs for X number of builds per builder".
A stopgap solution could be to have a cronjob run that looks something like this: 'find /some/buildbot/log/dir -mtime +7 | xargs rm'.
Buildbot does not currently age off or prune old log files. While the cronjob suggestion would work for now, it would be good to file a bug on buildbot.net about this. Having buildbot master monitor this during its continuous cycling would be easier to maintain. 

Also, whether it should prune by "date/age" or by "% available disk space" is unclear.
Blocks: 393044
Priority: -- → P3
Blocks: 400074
Found in triage.
Component: Testing → Release Engineering: Future
Product: Core → mozilla.org
QA Contact: testing → release
Version: unspecified → other
We currently do a nightly cronjob to clean up any log files that are older than 7 days.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.