On 2/28/2014 8:44 PM, John Schoenick wrote: > On 02/28/2014 05:40 PM, Daniel Holbert wrote: >> On 02/28/2014 05:32 PM, L. David Baron wrote: >>> Why not change the try repo reset procedure so that instead of just >>> cloning mozilla-central, you also pull from the old try repo into >>> the new one all of the heads of try pushes made within the last one >>> or two weeks. (Presumably there's a list of them somewhere, or it >>> could be maintained?) Then the try reset won't break things for >>> those recent pushes, but only the older ones. >> This seems like a good solution. >> >> One (possibly obvious) clarification: we'd need to rely on the pushlog >> DB (rather than the changeset datestamps) when creating the list of >> recent heads, since changeset datestamps are customizable and hence >> unreliable. > > Or taking this a step further, having a rolling cronjob |hg strip| > revisions not on m-c older than a certain date would remove the need > to perform resets entirely, and give a predictable date after which > your try push would disappear. You could even add a "keep me for N > days" parameter to try syntax for pushes that we'd like to stick around. > Note, we already investigated this some time ago[1], and "hg strip" doesn't interact well with the current pushlog hook. It's possible we could make this work if we changed the pushlog hook to accomodate.
-Ted 1. https://bugzilla.mozilla.org/show_bug.cgi?id=633161 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
