I handle status information for a single process.base.Builder object.
That object sends status changes to me (frequently as Events), and I
provide them on demand to the various status recipients, like the HTML
waterfall display and the live status clients. It also sends build
summaries to me, which I log and provide to status clients who aren't
interested in seeing details of the individual build steps.
I am responsible for maintaining the list of historic Events and
Builds, pruning old ones, and loading them from / saving them to
disk.
I live in the buildbot.process.base.Builder object, in the
.builder_status attribute.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generateFinishedBuilds(self,
branches=[ ] ,
num_builds=None,
max_buildnum=None,
finished_before=None,
max_search=200) |
source code
|
|
|
eventGenerator(self,
branches=[ ] ,
categories=[ ] ,
committers=[ ] ,
minTime=0)
This function creates a generator which will provide all of this
Builder's status events, starting with the most recent and
progressing backwards in time. |
source code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
newBuild(self)
The Builder has decided to start a build, but the Build object is not
yet ready to report status (it has not finished creating the Steps). |
source code
|
|
|
buildStarted(self,
s)
Now the BuildStatus object is ready to go (it knows all of its Steps,
its ETA, etc), so it is safe to notify our watchers. |
source code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Inherited from twisted.persisted.styles.Versioned :
__providedBy__ ,
versionUpgrade
|