phase1: run ForceBuilder on local worker

There is no reason to send this over the network to some remote worker,
incurring latency for a purely housekeeping task that should be done on
the buildmaster host.

Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>

diff --git a/phase1/master.cfg b/phase1/master.cfg
index 46a9f703c2eaeafcb72536c58bc3a7a4d17a2548..2b1b72a718537e6c814828b2ec687b327721eca0 100644 (file)
--- a/phase1/master.cfg
+++ b/phase1/master.cfg
@@ -38,6 +38,7 @@ from buildbot.steps.transfer import FileDownload
 from buildbot.steps.transfer import FileUpload
 from buildbot.steps.transfer import StringDownload
 from buildbot.worker import Worker
+from buildbot.worker.local import LocalWorker
 
 
 if not os.path.exists("twistd.pid"):
@@ -550,11 +551,14 @@ workerNames = [ ]
 for worker in c['workers']:
        workerNames.append(worker.workername)
 
+# add a single LocalWorker to handle the forcebuild builder
+c['workers'].append(LocalWorker("__local_force_build", max_builds=1))
+
 force_factory = BuildFactory()
 
 c['builders'].append(BuilderConfig(
        name        = "00_force_build",
-       workernames = workerNames,
+       workername  = "__local_force_build",
        factory     = force_factory))
 
 for target in targets: