RESOLVED FIXED 214921
Automatically delete old data from ews buildbot instance
https://bugs.webkit.org/show_bug.cgi?id=214921
Summary Automatically delete old data from ews buildbot instance
Aakash Jain
Reported 2020-07-29 08:30:32 PDT
Automatically delete old data from ews-build. We can choose a time range, maybe 1 year, after which the build logs will be deleted, the build and status-bubble information will still be retained, just the detailed build logs will be deleted. We can use Buildbot's JanitorConfigurator for that (https://docs.buildbot.net/latest/manual/configuration/configurators.html#janitorconfigurator).
Attachments
Patch (1.42 KB, patch)
2020-11-23 12:09 PST, Aakash Jain
no flags
Patch (1.42 KB, patch)
2020-11-27 10:36 PST, Aakash Jain
no flags
Radar WebKit Bug Importer
Comment 1 2020-07-29 08:30:57 PDT
Aakash Jain
Comment 2 2020-11-23 12:09:51 PST
Aakash Jain
Comment 3 2020-11-23 12:15:34 PST
Since currently most of the infrastructure is down and there is almost no load on the server, I took this opportunity to run this on the server as well to delete logs older than 1 year. See: https://ews-build.webkit.org/#/builders/54/builds/1 After deleting the logs, the status-bubbles are still fully functional, buildbot builds are still accessible, just that the individual steps in the buildbot builds wouldn't show the logs, e.g.: https://ews-build.webkit.org/#/builders/19/builds/1
Aakash Jain
Comment 4 2020-11-27 10:36:59 PST
Jonathan Bedard
Comment 5 2020-11-30 06:43:40 PST
Comment on attachment 414957 [details] Patch I like this change, it seems like a happy medium between outright deleting old builds entirely and keeping them around in some for to run analytics over them.
EWS
Comment 6 2020-11-30 07:05:11 PST
commit-queue failed to commit attachment 414957 [details] to WebKit repository.
EWS
Comment 7 2020-11-30 07:09:01 PST
Committed r270243: <https://trac.webkit.org/changeset/270243> All reviewed patches have been landed. Closing bug and clearing flags on attachment 414957 [details].
Note You need to log in before you can comment on or make changes to this bug.