Bug 12328 - Move configuration to fragments in core layer
Summary: Move configuration to fragments in core layer
Status: RESOLVED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 2.5
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 6.1 M1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-11-08 22:40 UTC by Joshua Lock
Modified: 2026-08-10 11:00 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock 2017-11-08 22:40:12 UTC
Replicate the configurations we use on the autobuilder to a set of configuration file fragments in the core metadata. 

The autobuilder configuration creation then becomes a simple matter of including the right files from the core metadata. This simplifies autobuilder logic as the core metadata will be responsible for providing working configurations and all the autobuilder has to do is include the correct configuration file to enable the configuration which is being built.
Comment 1 Joshua Lock 2018-02-22 10:20:08 UTC
Reassigning to Richard as he is driving the yocto-autobuilder-helper work. The priority of moving the configuration fragments into the metadata layers is reduced by the architecture of the helper scripts, therefore I've dropped priority to Medium and moved milestone to 2.6
Comment 2 Randy MacLeod 2023-10-24 14:24:52 UTC
Bulk move from 4.99 or 0.00 to 5.99
Comment 3 Richard Purdie 2026-08-10 11:00:17 UTC
Not complete but we do have fragments covering a decent chunk of config now and will migrate more if/as/when it makes sense: https://git.openembedded.org/openembedded-core/log/meta/conf/fragments