[yocto] Autobuilder migration status.

[Flanagan, Elizabeth]

All,

I wanted to give people an update on the new autobuilder codebase and the
migration that occurred this weekend. As you may know, over the past few
months, I've been rewriting the autobuilder to be more maintainable,
faster, and easier to extend. As off this weekend, the new autobuilder code
is now active at http://autobuilder.yoctoproject.org:8011 and is the main
autobuilder for published artifacts. We still have the meta-intel builds
building off of the old autobuilder, however that will switch over later
this week. There is still one outstanding old feature that needs to be
implemented (buildhistory collection) and one known bug (relating to how
git archives derive hash values for their name) but both of those will be
fixed/added relatively soon. I'll also be implementing some additional
features (automailing QA teams when we have release builds starting is next
on that list so I quit forgetting to send out the email :) adding a
randomized builder, etc ) in the coming weeks. These will hopefully be
available prior to 1.4.

Unfortunately, the migration caused us to run a little bit behind in our
1.4_M5.rc build. There were some minor networking issues with one builder
that Michael Halstead fixed. The new system also exposed some race
conditions within sanity testing which Richard has taken the past day or so
to squish. And lastly the the migration exposed some bugs in the
autobuilder code base. While bugs were not entirely unexpected, this did
delay the 1.4_M5.rc1 build slightly. Those bugs (except for the git archive
naming) should be resolved as of this afternoon and I believe Richard has
fixed sanity testing. Of course, there may be more things we uncover, but
they will be fixed as we uncover them.

There is one new feature that I want to make people aware of. We now have
the ability to "mix and match" layer branches. Before, I required the
maintainers of every layer to maintain a 1.x_Mx release branch. I can now
utilize other branches with the new codebase (ie build 1.4_M5 poky
utilizing master for meta-intel). I would prefer it if people still
maintained milestone release branches, however, if you decide to change how
you want to branch, I can support your workflow as long as you let me know.
I will still want people to maintain a final release branch (danny, denzil,
etc), however, we can now support different branching policies.

If you want to start up your own autobuilder, please be aware that the
config file format is, at this moment, only partially documented. I'll be
working on full documentation this coming month in preparation for the 1.4
release. However, there are enough code samples and sample configs that
creating a new setup is fairly easy. buildset-config and
lib/python2.7/site-packages/autobuilder/buildsteps/HelloWorld.py are your
friends here.

Current plans are to have meta-intel up tomorrow on the new code base, and
bug fixing/feature addition continuing for the next few days. If you have
any questions, please, let me know. Thanks.

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130320/4510c296/attachment.html>