On Fri, May 11, 2018 at 7:47 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> On 5/11/18 7:06 PM, Gregory Szorc wrote: > >> Artifact retention and expiration boils down to a >> trade-off between the cost of storage and the convenience of accessing >> something immediately (as opposed to waiting several dozen minutes to >> populate the cache). >> > > Just to be clear, when doing a bisect, one _can_ just deal with local > builds. But the point is that then it takes tens of minutes per build as > you point out. So a bisect task that might otherwise take 10-15 minutes > total (1 minute per downloaded build) ends up taking hours... And this is where bisect-in-the-cloud would come in. You could trigger dozens of builds on Taskcluster and they would all come back in the time it takes a single build to run. Or you codify the thing you are testing for, submit it to bisect-in-the-cloud, and it does everything for you and reports on the results. It still might take dozens of minutes to a few hours. But at least you wouldn't be burdened with the overhead of doing everything manually. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
