Would removing those files affect the ability of mozregression to locate pushes of old regressions?
- Xidorn On Wed, May 9, 2018, at 4:49 PM, ntho...@mozilla.com wrote: > We have approximately 400 TB of old files in the two directories > firefox/tinderbox-builds and mobile/tinderbox-builds on > archive.mozilla.org [1,2]. I'm suggesting it's time to remove them. > > The files come from pushes into the gecko repositories when the builds & > tests were run on Buildbot. The subdirectories for mozilla-inbound and > mozilla-central go as far back as September 2015, and up to August 2017, > although the later dates may only contain test logs. Others are for > discontinued branches like b2g-inbound, graphics, and fx-team. We used a > 30 day retention policy until Sep 2015, when the backend storage for > archive.m.o was migrated to AWS S3 (at that time S3 did not have the > lifecycle management feature). > > As the build jobs were gradually moved to Taskcluster the artifacts > moved into the Taskcluster index, which has a retention period of 1 > year. For some platforms there is now a gap between the old buildbot > files and the taskcluster ones. eg linux64 on buildbot goes up to > January 2017, and taskcluster starts at May 2017. > > I'd like to remove the two tinderbox-builds directories. Please respond > if you know of any reasons we should not proceed. > > [1] https://archive.mozilla.org/pub/firefox/tinderbox-builds/ > [2] https://archive.mozilla.org/pub/mobile/tinderbox-builds/ > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
