Maybe what is needed is a way to specify per builder the chroot to use. That way, to do bootstrapping we would need a way to specify a custom chroot for a specific builder and a way to dispatch a build to that builder. The rest of the build farm could continue it's normal activity at that time.
The problem is that when doing a bootstrap build we seem to use a custom chroot that must not be used by any other build.
There is a race when enablement returns a builders, it comes back automatically in automatic and could get a build dispatched using the custom chroot.
(See https:/ /wiki.canonical .com/Informatio nInfrastructure /OSA/Bootstrapp ingPackages for the process.)
Maybe what is needed is a way to specify per builder the chroot to use. That way, to do bootstrapping we would need a way to specify a custom chroot for a specific builder and a way to dispatch a build to that builder. The rest of the build farm could continue it's normal activity at that time.