188.8.131.52 Bzr Hook
Bzr is also written in Python, and the Bzr hook depends on Twisted to send the
To install, put
contrib/bzr_buildbot.py (see Contrib Scripts) in one
of your plugins locations a bzr plugins directory (e.g.,
~/.bazaar/plugins). Then, in one of your bazaar conf files (e.g.,
~/.bazaar/locations.conf), set the location you want to connect with
buildbot with these keys:
- one of 'commit', 'push, or 'change'. Turns the plugin on to report changes via
commit, changes via push, or any changes to the trunk. 'change' is
- (required to send to a buildbot master) the URL of the buildbot master to
which you will connect (as of this writing, the same server and port to which
- (optional, defaults to 9989) the port of the buildbot master to which you will
connect (as of this writing, the same server and port to which slaves connect)
- (optional, defaults to not pqm) Normally, the user that commits the revision
is the user that is responsible for the change. When run in a pqm (Patch Queue
Manager, see https://launchpad.net/pqm) environment, the user that commits is
the Patch Queue Manager, and the user that committed the *parent* revision is
responsible for the change. To turn on the pqm mode, set this value to any of
(case-insensitive) "Yes", "Y", "True", or "T".
- (optional, defaults to not a dry run) Normally, the post-commit hook will
attempt to communicate with the configured buildbot server and port. If this
parameter is included and any of (case-insensitive) "Yes", "Y", "True", or
"T", then the hook will simply print what it would have sent, but not attempt
to contact the buildbot master.
- (optional, defaults to not sending the branch name) If your buildbot's bzr
source build step uses a repourl, do *not* turn this on. If your buildbot's
bzr build step uses a baseURL, then you may set this value to any of
(case-insensitive) "Yes", "Y", "True", or "T" to have the buildbot master
append the branch name to the baseURL.
Note: The bzr smart server (as of version 2.2.2) doesn't know how to resolve
bzr:// urls into absolute paths so any paths in
won't match, hence no change notifications will be sent to Buildbot. Setting
configuration parameters globally or in-branch might still work.
When buildbot no longer has a hardcoded password, it will be a configuration
option here as well.
Here's a simple example that you might have in your
buildbot_on = change
buildbot_server = localhost