On 2015-11-06 5:56 PM, Mark Finkle wrote:
I also think measuring build times, and other build related stats, would be
useful. I'd like to see Mozilla capturing those stats for developer builds
though. I'm less interested in build times for the automation. That data is
already looked at by the automation team.
Chris Manchester has volunteered to look into submitting build times in
automation to perfherder here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1222549
I actually do think that perfherder has some advantages over the
existing grafana system, in that it has the capability of being
sheriffed easily down to the per-commit level by anyone (not just
releng/ateam).
We'll see I guess! The proof will be in bugs filed and fixed when
regressions occur. I really think developer build times are strongly
correlated with build times in automation, so my hope is that there will
be a trickle-down effect if this system proves useful.
Build stats for developers is a black hole though. We don't have a good
idea of the amount of time it takes developers, and this is likely
something that could end up driving productivity down and keep new
contributors from getting involved.
I've heard the same from developers in the Toronto office. I'm honestly
not sure how helpful tracking developer build times via some
telemetry-like system would be: everyone knows that things have gotten
worse over the last year or so, the question is how do we address that?
Will
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
