Create a new build output history reporting class, using testlab.bbclass
from meta-oe as a base. This records information from images produced by
the build process in text files structured suitably for tracking within
a git repository, thus enabling monitoring of changes over time.
Build history c
Op 2 dec. 2011, om 00:56 heeft Paul Eggleton het volgende geschreven:
> Create a new build output history reporting class, using testlab.bbclass
> from meta-oe as a base. This records information from images produced by
> the build process in text files structured suitably for tracking within
> a
On Friday 02 December 2011 11:03:34 Koen Kooi wrote:
> I know I forgot to update it, but that should be: 2007 - 2011
OK, I have updated this in the branch.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
Openembedded-core maili
Op 2 dec. 2011, om 00:56 heeft Paul Eggleton het volgende geschreven:
>
> +buildhistory_commit() {
> + ( cd ${BUILDHISTORY_DIR}/
> + git add ${BUILDHISTORY_DIR}/*
> + git commit ${BUILDHISTORY_DIR}/ -m "Build ${BUILDNAME} for
> machine ${MACHINE} configured for ${DIS
On Wednesday 07 December 2011 09:50:51 Koen Kooi wrote:
> One of the big problems with the old testlab code was that using multiple
> buildslaves created a huge mess for the git repo. What do you think about
> doing this the following before the 'git add'?
>
> git pull -q -s recursive -X theirs ${
On Wednesday 07 December 2011 09:50:51 Koen Kooi wrote:
> Op 2 dec. 2011, om 00:56 heeft Paul Eggleton het volgende geschreven:
> > +buildhistory_commit() {
> > + ( cd ${BUILDHISTORY_DIR}/
> > + git add ${BUILDHISTORY_DIR}/*
> > + git commit ${BUILDHISTORY_DIR}/ -m "Build ${BU
