multiconfig | Load configuration from multiple sources in Go | JSON Processing library

Ideally, layers shouldn't impact much the build system. Especially their order of inclusion in BBLAYERS, better if not at all. If you want recipes that depend on machines, look into COMPATIBLE_MACHINE or use appropriate machine overrides for variables (note you can't make a bbappend apply to COMPATIBLE_MACHINE but not the original recipe), if some are specific to some distro features, look into REQUIRED_DISTRO_FEATURES, etc...

You can make an init script wrapping oe-init-buildenv that leverages BBMASK to mask some parts of layers.

Best way is to make your layer nice to others, in which case you most probably don't need to care about including it or not depending on the presence of something else.

One can override default git location in the settings of the node.

Manage Jenkins -> Manage Nodes -> select windows node -> Configure -> Node properties in the lower part of the page.

Then check "Tool locations" checkbox and add path for default Git. Not sure, if spaces in paths are properly supported, didn't check.

Next tricky thing will be development of universal scripts, that run both in Linux Bash and in Windows CMD. Less tricky alternative is rewriting all my build scripts to some cross-platform language.

multiconfig allows the setups to run in parallel and the seventh setup is likely the "no multiconfig" setup which many people overlook when counting them.

multiconfig is not expected to generate parsing speed improvements, its designed to let you run multiple builds with parallelisation and a simple command. This is therefore not something which has been optimized or is planned to be optimized either, at least as things stand as that isn't an area where we can see optimizations we can make.