3.3.1. Master Organization
Buildbot makes heavy use of Twisted Python’s support for services - software modules that can be started and stopped dynamically. Buildbot adds the ability to reconfigure such services, too - see Reconfiguration. Twisted arranges services into trees; the following section describes the service tree on a running master.
18.104.22.168. BuildMaster Object
The hierarchy begins with the master, a
instance. Most other services contain a reference to this object in their
master attribute, and in general the appropriate way to access other
objects or services is to begin with
self.master and navigate from there.
The master has a number of useful attributes:
buildbot.process.metrics.MetricLogObserverinstance that handles tracking and reporting on master metrics.
buildbot.process.caches.CacheManagerinstance that provides access to object caches.
buildbot.pbmanager.PBManagerinstance that handles incoming PB connections, potentially on multiple ports, and dispatching those connections to appropriate components based on the supplied username.
buildbot.worker.manager.WorkerManagerinstance that provides wrappers around multiple master-worker protocols (e.g. PB) to unify calls for them from higher level code.
buildbot.changes.manager.ChangeManagerinstance that manages the active change sources, as well as the stream of changes received from those sources. All active change sources are child services of this instance.
buildbot.process.botmaster.BotMasterinstance that manages all of the workers and builders as child services.
The botmaster acts as the parent service for a
master.botmaster.brd), as well as all active workers (
buildbot.worker.AbstractWorkerinstances) and builders (
buildbot.schedulers.manager.SchedulerManagerinstance that manages the active schedulers. All active schedulers are child services of this instance.
buildbot.process.users.manager.UserManagerManagerinstance that manages access to users. All active user managers are child services of this instance.
buildbot.process.debug.DebugServicesinstance that manages debugging-related access – the manhole, in particular.
This is the ID for this master, from the
masterstable. It is used in the database and messages to uniquely identify this master.