Re: [Openembedded-architecture] [bitbake-devel] proposal: build pipelines in bitbake-setup

Alexander Kanavin <[email protected]> Thu, 7 May 2026 15:51:26 +0200
Newsgroups org.yoctoproject.lists.yocto,org.openembedded.lists.bitbake-devel
Message-ID <CANNYZj_wSR8fYqcXs7v5KrSYNC6xmkPZrvsU_3Gy92g6-WFWrg@mail.gmail.com>
On Thu, 7 May 2026 at 15:20, Richard Purdie
<[email protected]> wrote:
> The trouble is there are multiple things a user may want to do and
> which one is a hard choice to make. If you have some narrow layer with
> a specific image and application, that is easy. If you have a general
> layer like meta-virtualization, it is unclear which target(s) a given
> user may want. nodistro/poky face the same challenge, the thing the
> user might want "depends".

For such general layers two things come to mind:

1. An example/demo/starting point for one or a handful of most common
use cases. E.g. poky/nodistro would showcase two or three most common
core- images.

2. Running tests for locally made changes, before submitting a patch.
For oe-core/poky that's perhaps unrealistic, but I can imagine
something domain-specific like meta-virtualization could define steps
for this: $ bitbake-setup run test

Alex