[yocto] [AB PATCH 06/27] Autobuilder.py/Buildset.py: More sane parser/UI

[Bryan Evenson]

Beth,

> -----Original Message-----
> From: yocto-bounces at yoctoproject.org [mailto:yocto-
> bounces at yoctoproject.org] On Behalf Of Elizabeth Flanagan
> Sent: Wednesday, March 05, 2014 1:23 PM
> To: yocto at yoctoproject.org
> Subject: [yocto] [AB PATCH 06/27] Autobuilder.py/Buildset.py: More sane
> parser/UI
> 
> From: Beth Flanagan <elizabeth.flanagan at intel.com>
> 
> The parser for Autobuilder.py didn't dive very deep on triggered builds. If it
> found one, it just grabbed it's properties and then displayed them on the UI.
> This allowed us to mix and match repos/branches/commits.
> 

I'm a little unclear what functionality is being removed.  After this commit, are we still able to specify a different repo/branch/commit for each layer?  Or was the previous functionality to mix and match repo/branch/commits within a layer?  For example, would a buildset still be able to specify the repos as follows:

repos: [{'poky': 
            {'repourl':'git://git.yoctoproject.org/poky', 
             'branch':'dora'}},
        {'meta-openembedded': 
            {'repourl':'git://git.openembedded.org/meta-openembedded', 
             'branch':'dora'}}]

which have a different repository for each layer?  Or do something like:
repos: [{'poky': 
            {'repourl':'git://git.yoctoproject.org/poky', 
             'branch':'dora'}},
        {'meta-openembedded': 
            {'repourl':'git://git.openembedded.org/meta-openembedded', 
             'branch':'master'}}]

to specify different branches for each layer?  Granted, probably not a good idea for poky and meta-openembedded, but would be necessary for private layers that don't follow the same branch naming scheme. 

And as you had stated this is a fairly large patchset with some interface changes.  What are the plans (short-term and long-term) for the Autobuilder documentation?  Is the plan just to update the README files, or are there plans to move toward an HTML document under http://www.yoctoproject.org/documentation?  Either way, the Autobuilder documentation is pretty sparse and as an Autobuilder user I'm willing to extend the documentation.  If there are specific sections you are looking to document first, let us know.

Thanks,
Bryan