[Openembedded-architecture] consolidated configs

[Richard Purdie]

On Mon, 2016-03-21 at 15:33 -0400, Trevor Woerner wrote:
> Hi,
> 
> I'm curious to know what the best procedure is to propose and carry
> -out a new
> feature request for OE (or perhaps propose it, discuss, then decide
> it's not
> necessary)?
> 
> I haven't fleshed out all the nuances, but ideally I'd like to be
> able to give
> someone one file, they would run bitbake on it, and end up with a
> duplicate of
> my build (which generated that configuration file).
> 
> My use-case is CI builds. On one machine I do work on a build but
> when I want
> to transfer that to my CI there's too many manual steps involved
> (steps that I
> invariably get wrong). E.g. I don't always remember that in order to
> fix some
> issue I had to both tweak local.conf and add another layer, so on my
> CI
> machine I tweak local.conf but forget to add the necessary layer. Or
> I'll add
> the layer to bblayers.conf but then forget to actually checkout the
> layer for
> my CI build. I am familiar with the 'repo' tool, but 'repo' knows
> nothing
> about OE, so it's not a complete solution either. 'repo' might form
> part of
> the solution, but isn't a solution by itself.
> 
> Obviously this doesn't help if my build is based on internal layers
> or
> private layers and/or commits that only exist on my build machine.
> But even
> in this case the metadata that my build would generate would be
> sufficient for
> you (or whatever code we add) to recognize that these objects are not
> available (either by looking at a repository's remote information, or
> by
> looking at the hash of the HEAD which isn't found in a fresh
> checkout/fetch).
> 
> Apparently others might be interested in this too? Perhaps the
> toaster people?

I'd suggest people have a look at:

http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/

Yes, there is quite a bit of "buildbot" specific stuff in there but I
know Beth has quite strongly abstracted the core configuration code
into something more modular.

For specific examples, http://git.yoctoproject.org/cgit.cgi/yocto-autob
uilder/tree/buildset-config.controller

or more specifically:

http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder/tree/buildset-co
nfig.controller/nightly-arm.conf

I know Beth has wondered about abstracting this so that it could work
generically or with buildbot/jenkins specific plugins.

Cc'ing Beth who can likely comment more.

Even if its not right in its current form, it would be great to come up
with one format that works for everyone rather than different ones.

I'd note that this code powers the yocto autobuilder, which does test
quite some number of configurations.

Cheers,

Richard