If you customized an existing component (see
../manual/customization) or created a new component that you believe might be useful for others, you have two options:
Here we cover the second option.
To begin with, you must package your changes. If you do not know what a Python package is, these two tutorials will get you going:
The former is more recent and, while it addresses everything that you need to know about Python packages, is still work in progress. The latter is a bit dated, though it was the most complete guide for quite some time available for Python developers looking to package their software.
You may also want to check the sample project, which exemplifies the best Python packaging practices.
Buildbot supports several kinds of pluggable components:
(these are described in
which is described in
web server configuration <../manual/configuration/www>.
Once you have your component packaged, it's quite straightforward: you just need to add a few lines to the
entry_points parameter of your call of
setup function in
(You might have seen different ways to specify the value for
entry_points, however they all do the same thing. Full description of possible ways is available in setuptools documentation.)
setup.py <master/setup.py> file is updated, you can build and install it:
$ python setup.py build $ sudo python setup.py install
(depending on your particular setup, you might not need to use
After that the plugin should be available for Buildbot and you can use it in your
This is the last step before the plugin is available to others.
Once again, there is a number of options available for you:
python setup.py sdist)
The last option is probably the best one since it will make your plugin available pretty much to all Python developers.
Once you have published the package, please send a link to buildbot-devel mailing list, so we can include a link to your plugin to