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
Consequently, having the variable in your environment is the only way for
the janitor to parse and use the same configuration files as the controller.
Thomas
On Thu, Aug 1, 2019 at 7:33 AM akuster <akus...@mvista.com> wrote:
>
>
> On 7/30/19 11:36 AM, Thomas Goodwin wrote:
> > 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.
>
> Any chance of updating documentation on how to use this?
>
> - armin
> >
> > Signed-off-by: Thomas Goodwin <btgood...@geontech.com>
> > ---
> > builders.py | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/builders.py b/builders.py
> > index 5765040..3d12969 100644
> > --- a/builders.py
> > +++ b/builders.py
> > @@ -15,7 +15,8 @@ maxsteps = 9
> > # Environment to pass into the workers, e.g. to load further local
> configuration
> > # fragments
> > extra_env = {}
> > -#extra_env = {"ABHELPER_JSON" : "config.json
> /home/pokybuild/config-local.json"}
> > +if os.environ.get('ABHELPER_JSON'):
> > + extra_env['ABHELPER_JSON'] = os.environ['ABHELPER_JSON']
> >
> > @util.renderer
> > def get_sstate_release_number(props):
>
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
