Re: [yocto-patches] [yocto-autobuilder-helper][PATCH v2 05/10] scripts: add vcontainer-tarball setup, integration, and publishing

On Fri, Jun 5, 2026 at 9:26 AM Richard Purdie via lists.yoctoproject.org
<[email protected]> wrote:

> On Mon, 2026-06-01 at 16:18 -0700, Tim Orling via lists.yoctoproject.org
> wrote:
> > From: Tim Orling <[email protected]>
> >
> > Introduce the vcontainer-tarball SDK plumbing used by container build
> > jobs. The vcontainer-tarball is a meta-virtualization-derived SDK
> > (modelled after buildtools-tarball) that ships the container build
> > toolchain so worker jobs do not need to rebuild it for every step.
> >
> >   * scripts/utils.py: add setup_vcontainer_tarball(), and add an
> >     env_glob keyword argument to setup_tools_tarball() and
> >     enable_tools_tarball() so the vcontainer-tarball can source its
> >     specific environment-setup-ci file rather than the universal
> >     glob.
> >   * scripts/run-config: source the vcontainer-tarball environment
> >     for build-targets / cmds / test-targets / plain-cmds steps,
> >     gated by a new NOVCONTAINER step variable so individual steps
> >     (such as the dashboard indexing step) can opt out independently
> >     of NOBUILDTOOLS.
> >   * scripts/shared-repo-unpack: invoke setup_vcontainer_tarball so
> >     workers extract the SDK during unpack.
> >   * scripts/publish-artefacts: publish the vcontainer-tarball
> >     artefact so downstream test jobs can fetch a stable SDK.
> >
> > AI-Generated: Claude Cowork Opus 4.7
> > Signed-off-by: Tim Orling <[email protected]>
> > ---
> >  config.json                |  1 +
> >  scripts/publish-artefacts  |  5 +++++
> >  scripts/run-config         | 19 +++++++++++++++++++
> >  scripts/shared-repo-unpack |  1 +
> >  scripts/utils.py           | 22 ++++++++++++++++++----
> >  5 files changed, 44 insertions(+), 4 deletions(-)
> >
> > diff --git a/config.json b/config.json
> > index 7df4271..16d8a04 100644
> > --- a/config.json
> > +++ b/config.json
> > @@ -1433,6 +1433,7 @@
> >              "step3" : {
> >                  "shortname" : "Populate/update dashboard site",
> >                  "NOBUILDTOOLS" : true,
> > +                "NOVCONTAINER" : true,
> >                  "EXTRACMDS" : ["${SCRIPTSDIR}/run-dashboard-index
> ${HELPERBUILDDIR}/../"]
> >              }
> >          },
>
> Why is this step needing to opt out of a vcontainer? vcontainers are
> only enabled for specific steps and off by default?
>
> I looked further and realised you're basically using a vcontainer
> everywhere as far as I can tell? Why do we want to have the overhead of
> doing that outside of the vcontainer builds?
>
> For buildtools, it makes sense we need it everywhere except where we
> configure otherwise but I think for vcontainer, you want to opposite,
> you only use it in jobs where we actually need/use it?
>
>
The simple answer is that the 'buildtools' pattern was followed and an
attempt
was made to reuse the 'buildtools' code as much as possible. Upon further
review, the 'extratools' pattern is a better fit. This was addressed in v3.

Cheers,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#4153):
> https://lists.yoctoproject.org/g/yocto-patches/message/4153
> Mute This Topic: https://lists.yoctoproject.org/mt/119603244/924729
> Group Owner: [email protected]
> Unsubscribe:
> https://lists.yoctoproject.org/g/yocto-patches/leave/13169857/924729/1023951714/xyzzy
> [[email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>