![]() config-intelqa on x86-64 is an extension to config.json where it contains the recipes and meta layers to build core-image-sato-sdk on various supported architectures in Yocto Project. This is an initial release model on specifying the recipes use to build the embeddded linux images starting with x86-64 MTURBOT64 (Intel IA). With this reference, community will inherit the structure and model benchmark from config-intelqa-<arch>-lava.json to support and build own hardware on other architectures (e.g arm64, mips64, pcc, x86) on the same common CI infrastructure (Yocto Autobuilder). The config-intelqa-<arch>-lava.json will contain the consolidate data in autobuilder and LAVA (Linaro) to execute independent jobs configuration respectively. Architecture owners are to work with the respective maintainers and review their automated hardware tests to ensure common structure is agree by the current and/or new community. Signed-off-by: Aaron Chan <aaron.chun.yew.chan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
---|---|---|
janitor | ||
lava | ||
lava-templates | ||
scripts | ||
config-intelqa-x86_64-lava.json | ||
config.json | ||
local-example.json | ||
README |
This repo is designed to work in conjuction yocto-autobuilder. Whilst yocto-autobuilder is designed to cover all releases, this repo has a branch per release and contains the hooks that do the actual build configuration and execution.
pre-commit-hook.sh can be used to verify the JSON before committing, symlink this to .git/hooks/pre-commit (ln -s ../../scripts/pre-commit-hook.sh .git/hooks/pre-commit).
Its likely most users will end up having to customise this repository for their needs. The scripts themselves should be more generically reusable, the config.json, less so as it represents the Yocto Project Autobuilder test matrix.
There are two customisation options possible, one is through variable substitution, the other is through overlaying configuration files. The standard config.json tries to at least allow substitution of the paths. A local-example.json is included to show how you could override these from a separate config file, simply passing:
ABHELPER_JSON="config.json local-example.json"
into the environment of the autobuilder.
ABHELPER_JSON="config.json /some/location/local.json"
would also allow customisation.
Authors: Richard Purdie richard.purdie@linuxfoundation.org Joshua Lock joshua.g.lock@intel.com