[oe] oestats as automated testing reporting tool (Was: testing branch 2011-01-20)

[Yury Bushmelev]

I have spent some time to looking over oestats client and server code.
Below are some ideas.

> I've thought about collecting testing results via oe-stats.
> We should collect following data:
> - machine
Already in oestats (bb MACHINE variable)

> - distro
Already in oestats (bb USERDISTRO variable)

> - target
Well.. This should be name of image which was built. We have it but it
is mixed with lots of other packages data.
Not sure about best way here. May be we should use bitbake cmdline
args here. I'll address this question to bitbake developers.

> - workstation (distro + arch)*
We have build arch in oestats already (BUILD_ARCH). I'll prefer
replace it with BUILD_SYS because we can use e.g.
darwin/freebsd/cygwin as build host later.
As there is no reliable way to get user's build host distro I'll ask
to introduce new bitbake variable (OESTATS_HOST_DISTRO?).

> - bitbake version*
Seems bb.__version__ should be enough. Should we send revision and
branch when using git version?

> - tester (builder) name
OESTATS_BUILDER

> - last successful build
Report may get this from database.

> - build type (clean/incremental)*
OESTATS_BUILD_TYPE?

> - current issues
Report may get this from database.

I've forget to note that we have METADATA_BRANCH and METADATA_REVISION
as well in oestats.

P.S.: Do we really need this in perspective of merging with yocto? Or
may be just use e.g. some spreadsheet/form on google instead?

-- 
Yury Bushmelev