As with a lot of things, I’m sure it all depends on the scope of the change. Personally, if I ‘own’ the original bbappend, then I consider if it’s worth establishing an override or some other similar

Since Docker was mentioned, I use the community's CROPS containers via Docker in GitLab CI on a shared build server, providing the builders' downloads and sstate caches to the team to accelerate their

#yocto

The CROPS changes are all upstream now, so I've put up an example gist here: https://gist.github.com/btgoodwin/028c3a63315a27cae3c5989455058eef. There are comments throughout the files, and I'm still

Hi Yann, Thanks for sharing! We're working through something similar using a tweak to the CROPS docker containers and GitLab-CI (we started with autobuilder 2, so we've actually merged quite a bit of

The original check of /proc/net/tcp did not work on a headless Ubuntu 18.04.02 server. This new check- -and-reset routine should be equivalent if the script is executed. The assumption of DISPLAY=:1 w

I'm not sure I follow. This collects everything into the worker's "builddir/yocto-autobuilder-helper" path (I think; I'm new to buildbot). My aim was to let the buildbot master the chance to SCM the c

Signed-off-by: Thomas Goodwin <btgoodwin@...> --- builders.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/builders.py b/builders.py index 16c1344..b57bed7 100644 --- a/builders.py +++

The previous fixes requires the user to set "no-layer-add" for a repo and then use ADDLAYER to insert the sub-repos (e.g., meta-openmbedded/meta-oe) as a two-part process. This means that you would al

The preceeding errors that would be shown should be enough to identify the problem since it would have been a problem running bitbake-layers add-layer, indicating a misconfiguration of config.json. Si

The return value from bitbakecmd was not being returned when errors occurred which allowed shared-repo-unpack to succeed despite the failure. This fix changes to check_call and a try-catch when attemp

The meta-openembedded has no top-level conf/layer.conf, so layer-config's attempt to add it fails (silently). Adding it to the config.json with no-layer-add set to true will bypass this silent failure

It's already there, this patch is to make it work as described: http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder2/tree/README-WALKTHROUGHS.md?h=contrib/tgoodwin/config-json-fixes#n79 Consequentl

Using absolute paths in ABHELPER_JSON with remote-loading now works; the paths are stripped to os.path.basename() before being provided to the builders. Signed-off-by: Thomas Goodwin <btgoodwin@geonte

This feature/fix allows the worker to download the autobuilder helper JSON files from the controller rather than having to store them in the yocto-autobuilder-helper repository. The process installs t

The readme suggests exporting this variable from the environment to expose multiple configuration JSON files but the intended behavior doesn't work without adding the variable to extra_env. Signed-off