LayerIndex/Checker: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
No edit summary
No edit summary
Line 25: Line 25:
** option: add field showing if the checker did run/run last
** option: add field showing if the checker did run/run last
** option: add field noting the error if it did not pass
** option: add field noting the error if it did not pass
** There seems to be either a bug in bitbake-layers layerindex-fetch or in the layerindex causing some dunfell projects to not complete the fetch
<pre>
<add log>
</pre>


* will do myself
* will do myself

Revision as of 14:21, 18 August 2020

This is a little project to increase the quality of the LayerIndex entries.

We do not have a name yet, so we just call it 'Checker' for now.

It uses existing tools and the guidelines documented e.g. in the BSP guides and in the existing tests/tooling.

Currently it does 3 things:

a) grep LAYERSERIES_COMPAT <layer>/conf/layer.conf

b) grep LAYERDEPENDS <layer>/conf/layer.conf

c) run layer check script: yocto-check-layer (from OE-core repo)


An example run is available on this page for 'dunfell' LayerIndex/Checker/dunfell


Next steps:

  • need help with:
    • Update layerindex to add field noting the layer passed the 'checker' (or however we will name it)
    • Expose api call to upload this for branch/layer/package combination
    • option: add field showing if the checker did run/run last
    • option: add field noting the error if it did not pass
    • There seems to be either a bug in bitbake-layers layerindex-fetch or in the layerindex causing some dunfell projects to not complete the fetch
<add log>


  • will do myself
    • update script to work against api
    • will host runner for layers.openembedded.org (weekly/stable branches ... master does not make too much sense atm).
    • enhance script to pick machines for BSP layers