You can set up a nextSlave function to assign slaves to a builder in a custom manner see: http://docs.buildbot.net/current/manual/cfg-builders.html#builder-configuration
I found the "Graceful Shutdown" button at: buildbot/buildslaves/<NAME> ...
What I read you suggesting is that one builder should checkout your source and then the other builders would depend on this first builder to get their source rather than perform their own checkout. I would advise against this. In effect this makes builders dependent on the files that are...
python,buildbot,email-notifications
There's no easy way to do this. However it is possible to do what you want: class MyMailNotifier(MailNotifier): def isMailNeeded(self, build, results): if build.properties.getProperty('scheduler') == '<SingleBranchSchedulerName>': return MailNotifier.isMailNeeded(self, build, results) else: return False While this code is not tested, I'm quite confident it does what you'd like....
Use a scheduler that has treeStableTimer set to the time span during which you want the scheduler to wait until the tree is no longer changing. For instance SingleBranchScheduler supports it. It is described as follows: treeStableTimer The scheduler will wait for this many seconds before starting the build. If...
Probably you are not using a version of Buildbot that supports collapseRequests. If I Google for it, I can only find references in the documentation for the development version of Buildbot. If you check that page, you'll see at the top there's a warning that the documentation is for the...
Solved it : since buildbot uses virtualenv, I needed to install pyOpenSSL via easy_install - in the directory that contains the local python env (i.e., the "sandbox") I ran "easy_install pyopenssl" and the SSL handshake proceeded correctly, so buildbot can send emails now. Initially, I "installed" pyOpenSSL by linking to...
unit-testing,testing,output,twisted,buildbot
You can format output from trial arbitrarily by writing a reporter plugin. You found the interface for that plugin already - IReporter. Once you write such a plugin, you'll be able to use it by adding --reporter=yourplugin to your trial command line arguments. You can see the list of reporter...
Merging Build Requests is the typical solution.
python,twisted,introspection,buildbot
Ok, so the problem is here: cls = getattr(sys.modules[__name__], build_options['build_type']) This does not work because exec makes it so that __name__ has the value "__builtin__". However, you can use globals() to get the current globals: cls = globals()[build_options['build_type']] For instance, if I add the following code into a brand new...
Yeah, that test needs to be decorated with @defer.inlineCallbacks. The newest version of Twisted (released after Buildbot-0.8.8) detects this as an error, whereas old versions just silently ignored it. The fix is https://github.com/buildbot/buildbot/commit/de8da868755810e453cbbb6c44793c53bb2f398b
If a Builder has two different checkouts, you must use the "codebase" feature. This will let you track two sourcestamps, one for each one. Are you using "codebase"?
Have a look at Source Stamp Properties There in changes you have access to these attributes. So in a custom buildStep you could do something like: def start(self): branch = self.getProperty('branch') revision = self.getProperty('revision') repository = self.getProperty('repository') changes = self.getProperty("changes") or [] # returns None if there are no changes...