Potential issues with two nightly per days?

[Sylvestre Ledru]

Hello,

Would it have a negative impact right now if you move to two (or more) nightly per day?

If yes, how could we get this work prioritized?

Merci
Sylvestre


Le 15/03/2017 à 14:47, Frank Bertsch a écrit :
>
>
>
>
> -------- Forwarded Message --------
> Subject: 	Re: Potential issues with two nightly per days?
> Date: 	Wed, 8 Mar 2017 13:43:52 -0500
> From: 	Frank Bertsch <fbertsch at mozilla.com>
> To: 	fhr-dev at mozilla.org
>
>
>
> For TMO (measurement and evolution views):
>
> Currently we aggregate build_ids by YYYYMMDD of the build (in the
> aggregates dataset [0]). So initially we would aggregate these distinct
> builds together, and you wouldn't be able to see them separately in TMO.
>
> Eventually we would need to have changes for both aggregation, storage,
> API, and front-end display to separate these builds. I would estimate it
> to be ~2 weeks of work.
>
> [0]
> https://github.com/mozilla/python_mozaggregator/blob/master/mozaggregator/aggregator.py#L337
>
>
> On 3/8/17 09:04, Sylvestre Ledru wrote:
> > Hello,
> >
> > With Pascal, we are working on potentially building two nightly per days. It would be great for the European community to
> > have builds in the morning to check new changes/fixes.
> >
> > Lawrence mentioned that it might impact you with telemetry. Is there anything we should be aware if we go ahead with this change?
> >
> > Thanks,
> > Sylvestre
> >
> >
> > _______________________________________________
> > fhr-dev mailing list
> > fhr-dev at mozilla.org
> > https://mail.mozilla.org/listinfo/fhr-dev
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/fhr-dev/attachments/20170315/350b71fa/attachment-0001.html>