there are some build information we can get from the deployed android.
11:03:19 liuyq:landing-panda$ adb shell getprop|grep build
[ro.build.characteristics]: [tablet,nosdcard]
[ro.build.date.utc]: [1326680337]
[ro.build.date]: [Mon Jan 16 02:18:57 UTC 2012]
[ro.build.description]: [pandaboard-eng 4.0.3 IML74K 31 test-keys]
[ro.build.fingerprint]: [pandaboard/pandaboard/pandaboard:4.0.3/IML74K/31:eng/test-keys]
[ro.build.host]: [ip-10-6-109-237]
[ro.build.product]: [pandaboard]
[ro.build.tags]: [test-keys]
[ro.build.type]: [eng]
[ro.build.user]: [jenkins-build]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [31]
[ro.build.version.release]: [4.0.3]
[ro.build.version.sdk]: [15]
11:08:52 liuyq:landing-panda$
should we add those to the result bundle?
Thanks,
Yongqin Liu
On 17 January 2012 07:59, Zygmunt Krynicki
<zygmunt.krynicki@linaro.org> wrote:
On 01/17/2012 12:33 AM, Michael Hudson-Doyle wrote:
On Mon, 16 Jan 2012 14:39:14 +0100, Zygmunt Krynicki<zygmunt.krynicki@linaro.org> wrote:
On Mon, Jan 16, 2012 at 2:25 PM, Paul Sokolovsky
<paul.sokolovsky@linaro.org> wrote:
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...
I always run around like a headless chicken asking for the same!
I think we should probably seriously think about how we can move things
in this direction. Something to talk about over coffee/beer at the
connect?
ZK