Hello Alexander,
On Tue, 17 Jan 2012 10:42:04 +0100 Alexander Sack asac@linaro.org wrote:
On Tue, Jan 17, 2012 at 4:14 AM, yong qin yongqin.liu@linaro.org wrote:
Hi, All
there are some build information we can get from the deployed android. like these: 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.display.id]: [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.id]: [IML74K] [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$
This reminds me:
can we replace or add something that includes our linaro-android build id? e.g. https://android-build.linaro.org/builds/~linaro-android/tracking-panda/#buil...
Blueprint or Bug?
I'd say a blueprint. We talked about something like that once, even more detailed info, like include manifest inside builds tarballs, so it was always possible to figure out what it was build from, similar to how kernel stores its git revision and config.gz.
And that's just one facet of the issue, another for example here: https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-whats-i... (in "permanent backlog"). Yesterday's task of getting build stats can be see as another facet. And in general, the task is providing more universally available metadata about the builds, by various means, and yes, I guess it makes sense to dedicate planning and implementation time for that, by making it a blueprint.