Bug 11745

Summary: nightly-refkit CreateBBLayersConf should be dynamic
Product: [Infrastructure] AutoBuilder Reporter: Stephano Cetola <stephano>
Component: autobuilderAssignee: Stephano Cetola <stephano>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: akuster, infras.ab.watcher, Infras.watcher, joshuagloe, mikko.ylinen, pidge
Version: unspecified   
Target Milestone: 2.4 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Stephano Cetola 2017-07-02 14:14:03 UTC
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.
Comment 1 Joshua Lock 2017-07-06 14:46:36 UTC
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.
Comment 2 Joshua Lock 2017-07-21 15:16:01 UTC
(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.
Comment 3 Stephano Cetola 2017-07-24 14:25:35 UTC
(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.
Comment 4 Joshua Lock 2017-07-24 14:33:37 UTC
Test one already happens on refkit's CI, whilst test two is the value add we provide by building on the Yocto AB.
Comment 5 Stephano Cetola 2017-07-25 15:22:29 UTC
*** Bug 11823 has been marked as a duplicate of this bug. ***
Comment 6 Armin Kuster 2017-07-25 23:02:56 UTC
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
Comment 7 Stephano Cetola 2017-08-07 15:01:13 UTC
Merged in 07c52d2b3ee445d84f24ad5c016f89615a52bab9