Since we are parsing and building all the images in refkit-ci.inc, a dynamic set of images is built. We should be adding layers to bblayers.conf dynamically to avoid errors as refkit-ci.inc changes.
refkit, quite nicely and correctly, uses TEMPLATECONF to provide a complete bblayers.conf We should probably have the autobuilder machinery be able to use the automatically generated bblayers.conf (and local.conf) from there.
(In reply to comment #1) > refkit, quite nicely and correctly, uses TEMPLATECONF to provide a complete > bblayers.conf > > We should probably have the autobuilder machinery be able to use the > automatically generated bblayers.conf (and local.conf) from there. The difficulty here is that we need to use the OE-Core and bitbake from the top-level directory, not those cloned as part of the refkit checkout.
(In reply to comment #2) > (In reply to comment #1) > > refkit, quite nicely and correctly, uses TEMPLATECONF to provide a complete > > bblayers.conf > > > > We should probably have the autobuilder machinery be able to use the > > automatically generated bblayers.conf (and local.conf) from there. > > The difficulty here is that we need to use the OE-Core and bitbake from the > top-level directory, not those cloned as part of the refkit checkout. Shouldn't we be doing both? I would think we'd want this setup: 1) Test refkit build exactly as they expect; with all their layers and revs. 2) Test meta-refkit with the HEAD of Yocto master Test 1 would ensure refkit builds as expected while test 2 would provide a "head's up" for future problems with Yocto.
Test one already happens on refkit's CI, whilst test two is the value add we provide by building on the Yocto AB.
*** Bug 11823 has been marked as a duplicate of this bug. ***
looks like it failed again. https://autobuilder.yocto.io/builders/nightly-refkit/builds/75/steps/BuildImages/logs/stdio NOTE: Starting bitbake server... ERROR: Layer 'refkit' depends on layer 'iot-web', but this layer is not enabled in your configuration ERROR: Layer 'refkit-gateway' depends on layer 'iot-web', but this layer is not enabled in your configuration
Merged in 07c52d2b3ee445d84f24ad5c016f89615a52bab9