Navigation

Since version 0.9.0 of Buildbot “slave”-based terminology is deprecated
in favor of “worker”-based terminology.

API change is done in backward compatible way, so old “slave”-containing
classes, functions and attributes are still available and can be used.
Old API support will be removed in the future versions of Buildbot.

Rename of API introduced in beta versions of Buildbot 0.9.0 done without
providing fallback.
See release notes for the list of breaking changes of private interfaces.

Use of obsolete names will raise Python warnings with category
buildbot.worker_transition.DeprecatedWorkerAPIWarning.
By default these warnings are printed in the application log.
This behaviour can be changed by setting appropriate Python warnings settings
via Python’s warnings module:

In general “Slave” and “Buildslave” parts in identifiers and messages were
replaced with “Worker”; “SlaveBuilder” with “WorkerForBuilder”.

Below is the list of changed API (use of old names from this list will work).
Note that some of these symbols are not included in Buildbot’s public API.
Compatibility is provided as a convenience to those using the private symbols
anyway.

In addition to class being renamed, environment variables that are set inside
container SLAVENAME and SLAVEPASS were renamed to
WORKERNAME and WORKERPASS accordingly.
Old environment variable are still available, but are deprecated and will be
removed in the future.

buildbot-worker has backward incompatible changes and requires buildmaster >= 0.9.0b8.
buildbot-slave from 0.8.x will work with both 0.8.x and 0.9.x versions of buildmaster, so there is no need to upgrade currently deployed buildbot-slaves during switch from 0.8.x to 0.9.x.