Losing 4 months of mozregression does sort of suck though. Being able to bisect down to a specific push is a lot more helpful than a specific nightly. I have it often enough that I'm annoyed by only having 1 year of builds.
What percentage of the space used for artifacts is actually builds that are used for mozregression vs other stuff (like debug builds)? Is there a way that we could somehow have different expiraries for the different kinds of data? 1 year for logs, debug symbols and debug builds seems very generous but 8 months for builds for mozregression seems stingy. -Jeff On Fri, Jun 26, 2020 at 3:01 PM Kartikaya Gupta <kgu...@mozilla.com> wrote: > > Thanks for clarifying. If nightlies are still available for that > period then I guess that's ok. It will be a slight inconvenience but > probably not worth the effort to and save those builds for a few > months. > > On Fri, Jun 26, 2020 at 9:53 AM Chris Cooper <c...@mozilla.com> wrote: > > > > I've received multiple replies about mozregression, so I'll provide > > some more context. > > > > Taskcluster artifacts expire by default after one year. This means the > > legacy cluster currently provides access to artifacts from June 26 to > > Nov 9, 2019 (Nov 9 was the cutover date to the new deployment). By > > shutting down the legacy cluster on July 3, we will be removing access > > to just over 4 months of artifacts. Note that this won't affect > > separate release archives like > > http://archive.mozilla.org/pub/firefox/. The end result for > > mozregression is that it will have fewer choices for intermediate > > builds while bisecting if it needs to reach back into that 4-month > > window and will need to rely on the nightlies. > > > > I looked at the specific S3 stats for older artifacts. I can't break > > mozregression usage out specifically, but over the past year we (all > > parties) have only accessed 19.04 GB of the 971.77 TB that are older > > than 180 days. > > > > cheers, > > -- > > coop > > > > On Fri, Jun 26, 2020 at 6:41 AM Kartikaya Gupta <kgu...@mozilla.com> wrote: > > > > > > Do these legacy artifacts include firefox builds that are used by > > > mozregression? It looks like there's still a reference to the old > > > taskcluster.net URL at > > > https://github.com/mozilla/mozregression/blob/3df977cf7b9c50bdbe8495cde17baeb6c5724be2/mozregression/config.py#L23 > > > which gets used. It would be valuable to ensure mozregression can > > > continue bisecting old builds after this decommissioning happens. > > > > > > On Thu, Jun 25, 2020 at 5:13 PM Chris Cooper <c...@mozilla.com> wrote: > > > > > > > > Hey all, > > > > > > > > You may recall that last fall we redeployed Taskcluster into two > > > > distinct clusters, one to support Firefox CI and another to handle > > > > Community projects[1]. We left the legacy deployment running to > > > > provide access to CI artifacts that would only be reachable via the > > > > old taskcluster.net interface. > > > > > > > > It turns out that we (Mozilla) don't access the legacy data very > > > > often: we are storing close to a petabyte of older artifacts in AWS > > > > and yet we access less than 25 GB of it. It costs us thousands of > > > > dollars every month for that storage, and several hundred dollars more > > > > to continue running the services to access it, so we've made a > > > > decision to decommission the legacy Taskcluster deployment a few > > > > months earlier than planned. > > > > > > > > We'll be shutting down the legacy services on July 3rd, 2020. That's > > > > one week from today. A week later on July 10, we will begin deleting > > > > the old artifacts. > > > > > > > > If you are one of the few individuals who does access artifacts from > > > > the legacy cluster and haven't already spoken to us about > > > > alternatives, please reach out before next Thursday. > > > > > > > > Note: this will *not* affect day-to-day CI on either the Firefox CI or > > > > Community clusters at all. > > > > > > > > Thanks, > > > > -- > > > > Chris Cooper > > > > Manager, Taskcluster @ Mozilla > > > > <c...@mozilla.com> > > > > > > > > 1. > > > > https://groups.google.com/g/mozilla.dev.platform/c/QhZFDhlQjxU/m/ngk8z6j1AgAJ > > > > _______________________________________________ > > > > firefox-dev mailing list > > > > firefox-...@mozilla.org > > > > https://mail.mozilla.org/listinfo/firefox-dev > > _______________________________________________ > > firefox-dev mailing list > > firefox-...@mozilla.org > > https://mail.mozilla.org/listinfo/firefox-dev > _______________________________________________ > 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
