test data request
asac at linaro.org
Mon Jan 16 12:55:32 UTC 2012
On Mon, Jan 16, 2012 at 1:44 PM, Paul Sokolovsky
<paul.sokolovsky at linaro.org> wrote:
> On Sun, 15 Jan 2012 21:14:05 +0100
> Zygmunt Krynicki <zygmunt.krynicki at linaro.org> wrote:
>> On Sun, Jan 15, 2012 at 7:48 PM, Alexander Sack <asac at linaro.org>
>> > On Sun, Jan 15, 2012 at 3:49 AM, Zach Pfeffer
>> > <zach.pfeffer at linaro.org> wrote:
>> >> Do you have a way we can dump the date and time of every build
>> >> that we've done?
>> >> Then we can take the data Zygmunt produced and merge it with that
>> >> data, and come up with our super cool graphs!
>> > Unfortunately, we don't have infinite history on android-build
>> > (think just 1 build).
>> > Not sure if we can grep some log from our server that isn't subject
>> > to our retention mechanisms?
>> > Maybe jenkins has more logs that date back longer?
>> I would recommend to store the build date as an attribute
>> 'android.build-date' in the standard format 'yyyy-mm-ddThh:mm:ssZ', we
>> can harvest that in lava and will build improved history for the
> 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?
On this front to remember to think about: How can we ensure that
bundles don't get lost if lava is temporarily down?
Technical Director, Linaro Platform Teams
http://www.linaro.org | Open source software for ARM SoCs
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
More information about the linaro-android