From 042fa495485de97a94994ba84b3eceb4ff2f4d8d Mon Sep 17 00:00:00 2001 From: Markus Katharina Brechtel Date: Mon, 4 May 2020 17:14:46 +0200 Subject: [PATCH] cleanup master config file --- templates/buildbot/master.cfg.j2 | 64 +++----------------------------- 1 file changed, 5 insertions(+), 59 deletions(-) diff --git a/templates/buildbot/master.cfg.j2 b/templates/buildbot/master.cfg.j2 index e786d90..8ee0537 100644 --- a/templates/buildbot/master.cfg.j2 +++ b/templates/buildbot/master.cfg.j2 @@ -1,55 +1,24 @@ # -*- python -*- # ex: set filetype=python: -from buildbot.plugins import * +{{ ansible_managed | comment}} -# This is a sample buildmaster config file. It must be installed as -# 'master.cfg' in your buildmaster's base directory. +from buildbot.plugins import * -# This is the dictionary that the buildmaster pays attention to. We also use -# a shorter alias to save typing. c = BuildmasterConfig = {} -####### WORKERS +c['workers'] = [] -# The 'workers' list defines the set of recognized workers. Each element is -# a Worker object, specifying a unique worker name and password. The same -# worker name and password must be configured on the worker. -c['workers'] = [ - worker.LocalWorker("local-worker",max_builds=1) -] - -# 'protocols' contains information about protocols which master will use for -# communicating with workers. You must define at least 'port' option that workers -# could connect to your master with this protocol. -# 'port' must match the value configured into the workers (with their -# --master option) c['protocols'] = {'pb': {'port': 9989}} -####### CHANGESOURCES - -# the 'change_source' setting tells the buildmaster how it should find out -# about source code changes. Here we point to the buildbot version of a python hello-world project. - c['change_source'] = [] #c['change_source'].append(changes.GitPoller( # 'git://github.com/buildbot/hello-world.git', # workdir='gitpoller-workdir', branch='master', # pollInterval=300)) -####### SCHEDULERS - -# Configure the Schedulers, which decide how to react to incoming changes. In this -# case, just kick off a 'runtests' build - c['schedulers'] = [] -####### BUILDERS - -# The 'builders' list defines the Builders, which tell Buildbot how to perform a build: -# what steps, and which workers can execute them. Note that any particular build will -# only take place on one worker. - c['builders'] = [] {% for builder_name in buildbot_builders.keys() %} @@ -90,30 +59,13 @@ c['schedulers'].append(schedulers.SingleBranchScheduler( {% endfor %} -####### BUILDBOT SERVICES - -# 'services' is a list of BuildbotService items like reporter targets. The -# status of each build will be pushed to these targets. buildbot/reporters/*.py -# has a variety to choose from, like IRC bots. - c['services'] = [] -####### PROJECT IDENTITY - -# the 'title' string will appear at the top of this buildbot installation's -# home pages (linked to the 'titleURL'). - -c['title'] = "covid-videoplattform CICD" +c['title'] = "buildbot title" c['titleURL'] = "https://github.com/covid-videoplattform" -# the 'buildbotURL' string should point to the location where the buildbot's -# internal web server is visible. This typically uses the port number set in -# the 'www' entry below, but with an externally-visible host name which the -# buildbot cannot figure out without some help. - c['buildbotURL'] = "https://{{buildbot_server_name}}/" -# minimalistic config to activate new web UI c['www'] = dict( port=8010, plugins = dict( @@ -126,12 +78,6 @@ c['www'] = dict( }, ) -####### DB URL - c['db'] = { - # This specifies what database buildbot uses to store its state. - # It's easy to start with sqlite, but it's recommended to switch to a dedicated - # database, such as PostgreSQL or MySQL, for use in production environments. - # http://docs.buildbot.net/current/manual/configuration/global.html#database-specification - 'db_url' : "{{buildbot_database_url}}", + 'db_url' : "{{buildbot_database_url}}", }