| Trees | Indices | Help |
|
|---|
|
|
object --+
|
process.properties.PropertiesMixin --+
|
process.buildstep.BuildStep --+
|
Blocker
Build step that blocks until at least one other step finishes.
@ivar upstreamSteps: a non-empty list of (builderName, stepName) tuples
identifying the other build steps that must
complete in order to unblock this Blocker.
@ivar idlePolicy: string: what to do if one of the upstream builders is
idle when this Blocker starts; one of:
"error": just blow up (the Blocker will fail with
status EXCEPTION)
"ignore": carry on as if the referenced build step
was not mentioned (or is already complete)
"block": block until the referenced builder starts
a build, and then block until the referenced build
step in that build finishes
@ivar timeout: int: how long to block, in seconds, before giving up and
failing (default: None, meaning block forever)
| Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from Inherited from Inherited from |
|||
| Static Methods | |
|
Inherited from |
| Class Variables | |
parms =
|
|
flunkOnFailure = True
|
|
upstreamSteps = Nonehash(x) |
|
idlePolicy =
|
|
timeout = Nonehash(x) |
|
VALID_IDLE_POLICIES =
|
|
|
Inherited from |
|
| Properties | |
|
Inherited from |
| Method Details |
x.__init__(...) initializes x; see help(type(x)) for signature
|
str(x)
|
repr(x)
|
Return true if buildStatus1 and buildStatus2 are from related builds, i.e. a Blocker step running in buildStatus2 should be blocked by an upstream step in buildStatus1. Return false if they are unrelated. Default implementation simply raises NotImplementedError: you *must* subclass Blocker and implement this method, because BuildBot currently provides no way to relate different builders. This might change if ticket #875 ("build flocks") is implemented. |
|
| Class Variable Details |
parms
|
| Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Wed Nov 21 16:22:47 2012 | http://epydoc.sourceforge.net |