Ticket #108 (new enhancement)

Opened 1 year ago

Last modified 1 year ago

Buildbot master should have the ability to delete aging logfiles

Reported by: bhearsum Assigned to:
Priority: major Milestone: undecided
Component: statusplugins Version: 0.7.6
Keywords: sql Cc:

Description

Buildbot logfiles can grow to be big fairly quickly. I think that the Buildbot master (and slaves?) should be capable of managing this. It would be nice to say "delete logfiles older than XXX" or "only keep logfiles for XXX number of builds" or "use a maximum of XXX GB for logs", etc.

Change History

11/01/07 00:55:41 changed by warner

I was wondering about this too.. with the flat-file backend we have now, a simple external cron job is sufficient (mine just delete files in the builder directories that are more than a month old.. also note that you can delete the log and leave the main build file there, and then you still get basic pass/fail info).

But the upcoming SQL backend will render this approach useless, so the buildbot has to take an active role in limiting db size.

What sort of options should we have? I'm planning on having a c['database'] or cstatus_database?}}} object of some sort, so we can stick options on it.

11/01/07 00:55:56 changed by warner

  • keywords set to sql.
  • owner changed.
  • version set to 0.7.6.
  • component changed from other to statusplugins.