Buildbot webhook handler for transifex API
Go to file
2022-12-28 08:04:44 +00:00
buildbot_transifex Initial transformation into transifex 2022-12-28 08:04:44 +00:00
.gitignore Added unittest for push events. 2018-09-05 11:47:58 +02:00
.travis.yml Setup travis ci 2019-03-11 02:03:46 +01:00
LICENSE Initial commit 2018-09-04 10:48:57 +02:00 Initial transformation into transifex 2022-12-28 08:04:44 +00:00
requirements.txt Setup travis ci 2019-03-11 02:03:46 +01:00 Bumped version to 1.7.2 2022-09-05 16:15:16 +02:00
testrequirements.txt Setup travis ci 2019-03-11 02:03:46 +01:00

Buildbot Transifex Plugin

PyPI version GitHub

This plugin for buildbot adds integration support with gitea, featuring push hooks, commit status updates and a change source.


pip install buildbot_gitea

This installs itself into the plugin discovery of buildbot, so no extra imports are required to get buildbot to find the plugin.


The following configuration shows how the different parts of the plugin can be set-up in the buildbot master.cfg:

from buildbot.plugins import *

c = BuildbotMasterConfig = {}
c['www'] = {
    'change_hook_dialects': {
        'gitea': {
            'secret': '<SecretToEnterInGitea>',
            'onlyIncludePushCommit': True

c['services'] = [
    # Report status back to gitea, verbose flag enables verbose output in logging for debugging
        '', "SECRET", verbose=True)

buildFactory = util.BuildFactory()


The webhook currently supports pushes and pull requests by default, but you can subclass buildbot_gitea.webhook.GiteaHandler to add supports for other events, and then use your subclass by setting the class parameter:


from buildbot_gitea.webhook import GiteaHandler
class MyGiteaHook(GiteaHandler)
    def process_whatever(self, payload, event_type, codebase):
        # This should be a list of dicts
        changes = []

        return changes

# master.cfg

from myhook import MyGiteaHook

c['www'] = {
    'change_hook_dialects': {
        'gitea': {
            'class': MyGiteaHook,
            # ...

Note that the handlers need to be named according to the scheme: process_{event} (e.g., process_create, etc).


Change Hook

The change hook is set as part of the www section in the change_hook_dialects named gitea.

Parameter Description
secret The secret, which needs to be set in gitea
onlyIncludePushCommit A push may have more than one commit associated with it. If this is true, only the newest (latest) commit of all received will be added as a change to buildbot. If this is set to false, all commits will inside the push will be added.
class Set this if you want to use your own handler class (see above for details)

In gitea in your project or organization and add a new webhook of type gitea. Set the parameters as follows:

Parameter Value
Target URL
POST Content Type application/json
Secret The secret from above

Change Source

The change source is part build step to clone a gitea repository. It includes features to build a pull request, if the pull request can be merged without conflicts. This needs to be used in conjunction with a gitea change_hook and have it send pull request updates in order to be able to handle pull requests.

The parameters for this are identical to the default git step from buildbot. It just uses information provided by the gitea change_hook to be able to handle pull requests.


The reporter sets the commit status of a commit inside of gitea, so in gitea a small icon will be displayed next to the commit message, indicating the build status.

The GiteaStatusPush is added to the services section of the global master config.

The parameters are as follows:

Parameter Value
URL The URL to the gitea instance.
token Generate an access token in the profile you want the buildbot to impersonate. Make sure the account in gitea has access to the repositories.
context Renderable The context is an identifier for this status, allowing to identify from which builder this came, defaults to Interpolate('buildbot/%(prop:buildername)s')
context_pr Renderable The context message to use, when building on a pull request, allowing to identify from which builder this came, defaults to Interpolate('buildbot/pull_request/%(prop:buildername)s')
warningAsSuccess Treat warnings as build as success to set in the build status of gitea. If false, warnings will be displayed as warnings.
verbose Perform verbose output


Gitea supports OAuth2 authentication so it is possible to have buildbot communicate to Gitea to authenticate the user.


from buildbot.plugins import util
c['www']['auth'] = util.GiteaAuth(
Parameter Value
endpoint The URL to your Gitea app. Something like
client_id The OAuth2 Client ID GUID, can be a Secret.
client_secret The OAuth2 Client Secret provided, when creating the OAuth application in gitea. Can be a Secret.