# -*- python -*- # ex: set syntax=python: # This is a sample buildmaster config file. It must be installed as # 'master.cfg' in your buildmaster's base directory (although the filename # can be changed with the --basedir option to 'mktap buildbot master'). # It has one job: define a dictionary named BuildmasterConfig. This # dictionary has a variety of keys to control different aspects of the # buildmaster. They are documented in docs/config.xhtml . # This is the dictionary that the buildmaster pays attention to. We also use # a shorter alias to save typing. c = BuildmasterConfig = {} ####### BUILDSLAVES # the 'slaves' list defines the set of allowable buildslaves. Each element is # a tuple of bot-name and bot-password. These correspond to values given to # the buildslave's mktap invocation. from buildbot.buildslave import BuildSlave c['slaves'] = [ BuildSlave("linux", "***"), BuildSlave("win32", "***") ] # to limit to two concurrent builds on a slave, use # c['slaves'] = [BuildSlave("bot1name", "bot1passwd", max_builds=2)] # 'slavePortnum' defines the TCP port to listen on. This must match the value # configured into the buildslaves (with their --master option) c['slavePortnum'] = 0000 ####### CHANGESOURCES # the 'change_source' setting tells the buildmaster how it should find out # about source code changes. Any class which implements IChangeSource can be # put here: there are several in buildbot/changes/*.py to choose from. from buildbot.changes.pb import PBChangeSource c['change_source'] = PBChangeSource() # For example, if you had CVSToys installed on your repository, and your # CVSROOT/freshcfg file had an entry like this: #pb = ConfigurationSet([ # (None, None, None, PBService(userpass=('foo', 'bar'), port=4519)), # ]) # then you could use the following buildmaster Change Source to subscribe to # the FreshCVS daemon and be notified on every commit: # #from buildbot.changes.freshcvs import FreshCVSSource #fc_source = FreshCVSSource("cvs.example.com", 4519, "foo", "bar") #c['change_source'] = fc_source # or, use a PBChangeSource, and then have your repository's commit script run # 'buildbot sendchange', or use contrib/svn_buildbot.py, or # contrib/arch_buildbot.py : # #from buildbot.changes.pb import PBChangeSource #c['change_source'] = PBChangeSource() ####### SCHEDULERS ## configure the Schedulers from buildbot.scheduler import Scheduler schedTrunk = Scheduler( name = "1.1-trunk", branch = "trunk", treeStableTimer = 1*60, builderNames = ["linux-trunk", "win32-trunk"] ) schedStable = Scheduler( name = "1.0-stable", branch = "branches/sourcemod-1.0.x", treeStableTimer = 1*60, builderNames = ["linux-stable", "win32-stable"] ) c['schedulers'] = [schedStable, schedTrunk] ####### BUILDERS # the 'builders' list defines the Builders. Each one is configured with a # dictionary, using the following keys: # name (required): the name used to describe this bilder # slavename (required): which slave to use, must appear in c['bots'] # builddir (required): which subdirectory to run the builder in # factory (required): a BuildFactory to define how the build is run # periodicBuildTime (optional): if set, force a build every N seconds # buildbot/process/factory.py provides several BuildFactory classes you can # start with, which implement build processes for common targets (GNU # autoconf projects, CPAN perl modules, etc). The factory.BuildFactory is the # base class, and is configured with a series of BuildSteps. When the build # is run, the appropriate buildslave is told to execute each Step in turn. # the first BuildStep is typically responsible for obtaining a copy of the # sources. There are source-obtaining Steps in buildbot/steps/source.py for # CVS, SVN, and others. from buildbot.process import factory from buildbot.steps.shell import Compile from buildbot.steps.shell import ShellCommand from buildbot.steps.transfer import FileDownload from buildbot.steps.source import SVN from buildbot.process.properties import WithProperties from buildbot.steps.python_twisted import Trial from buildbot import locks pdb_lock = locks.MasterLock("symbolstore") def create_factory(sep, os): f1 = factory.BuildFactory() f1.addStep(SVN(baseURL = "svn://svn.alliedmods.net/am/sourcemod/", mode = "copy" ) ) f1.addStep(ShellCommand( haltOnFailure = 1, name = "bootstrap", command = ["tools" + sep + "buildbot" + sep + "bootstrap.pl"], description = "bootstrapping", descriptionDone = "bootstrapped" )) f1.addStep(ShellCommand( haltOnFailure = 1, name = "build", command = ["tools" + sep + "buildbot" + sep + "startbuild.pl"], description = "compiling", descriptionDone = "compiled" )) f1.addStep(ShellCommand( haltOnFailure = 1, name = "upload", command = ["tools" + sep + "buildbot" + sep + "package.pl", ".." + sep + ".." + sep + "smdrop_info" ], description = "packaging", descriptionDone = "uploaded" )) if os == "win32": f1.addStep(ShellCommand( haltOnFailure = 1, locks = [pdb_lock], name = "symstore", command = ["tools" + sep + "buildbot" + sep + "symstore.pl"], description = "symstore", descriptionDone = "symstore" )) return f1 facWin = create_factory("\\", "win32") facLinux = create_factory("/", "linux") buildLinuxStable = { 'name': 'linux-stable', 'slavename': 'linux', 'builddir': 'linux-stable', 'factory': facLinux } buildLinuxTrunk = { 'name': "linux-trunk", 'slavename': "linux", 'builddir': "linux-trunk", 'factory': facLinux } buildWindowsStable = { 'name': 'win32-stable', 'slavename': 'win32', 'builddir': 'win32-stable', 'factory': facWin } buildWindowsTrunk = { 'name': "win32-trunk", 'slavename': "win32", 'builddir': "win32-trunk", 'factory': facWin } c['builders'] = [buildLinuxTrunk, buildWindowsTrunk, buildLinuxStable, buildWindowsStable] ####### STATUS TARGETS # 'status' is a list of Status Targets. The results of each build will be # pushed to these targets. buildbot/status/*.py has a variety to choose from, # including web pages, email senders, and IRC bots. c['status'] = [] from buildbot.status import html c['status'].append(html.WebStatus(http_port=8010)) # from buildbot.status import mail # c['status'].append(mail.MailNotifier(fromaddr="buildbot@localhost", # extraRecipients=["builds@example.com"], # sendToInterestedUsers=False)) # # from buildbot.status import words # c['status'].append(words.IRC(host="irc.example.com", nick="bb", # channels=["#example"])) # # from buildbot.status import client # c['status'].append(client.PBListener(9988)) ####### DEBUGGING OPTIONS # if you set 'debugPassword', then you can connect to the buildmaster with # the diagnostic tool in contrib/debugclient.py . From this tool, you can # manually force builds and inject changes, which may be useful for testing # your buildmaster without actually commiting changes to your repository (or # before you have a functioning 'sources' set up). The debug tool uses the # same port number as the slaves do: 'slavePortnum'. #c['debugPassword'] = "debugpassword" # if you set 'manhole', you can ssh into the buildmaster and get an # interactive python shell, which may be useful for debugging buildbot # internals. It is probably only useful for buildbot developers. You can also # use an authorized_keys file, or plain telnet. #from buildbot import manhole #c['manhole'] = manhole.PasswordManhole("tcp:9999:interface=127.0.0.1", # "admin", "password") ####### PROJECT IDENTITY # the 'projectName' string will be used to describe the project that this # buildbot is working on. For example, it is used as the title of the # waterfall HTML page. The 'projectURL' string will be used to provide a link # from buildbot HTML pages to your project's home page. c['projectName'] = "SourceMod" c['projectURL'] = "http://www.sourcemod.net/" # the 'buildbotURL' string should point to the location where the buildbot's # internal web server (usually the html.Waterfall page) is visible. This # typically uses the port number set in the Waterfall 'status' entry, but # with an externally-visible host name which the buildbot cannot figure out # without some help. c['buildbotURL'] = "http://localhost:8010/"