On Mon, 16 Jan 2012 13:55:32 +0100 Alexander Sack asac@linaro.org wrote:
[]
If it would useful to start doing that from now on, yes that can be added. Otherwise, we'd need to join LAVA and Android Build data anyway, and primary key is (job_name, build_no), which is already present in LAVA (in the form of build URL).
Yes, having our build data go into central lava database next to the test results etc. can only be beneficial and would be awesome. Would we replay the data for the builds of last three month?
Long time ago I proposed that LAVA to become the CI central, collecting and displaying all the needed data, instead of random-patching Android Build to display CI data. That didn't catch much attention then...
On this front to remember to think about: How can we ensure that bundles don't get lost if lava is temporarily down?