4 Jan 2006 09:30
[Python-Dev] buildbot
> Currently, branches are not supported, because buildbot is > somewhat limited. When I get a solution for this problem, > I plan to have all buildbots build both the trunk and the > 2.4 branch; such builds would only be initiated whenever > something is committed on the branch. Branch support appeared fairly recently (buildbot-0.7.0, about two months ago), and I believe it should be sufficient to trigger builds for both the trunk and the 2.4 branch. The last part of the setup involves modifying the svn_buildbot.py hook script, though, so I won't claim this support is complete yet. The basic idea is that you create multiple Scheduler instances, one for each branch you want to monitor. Both Schedulers are configured to trigger all the Builders. You configure the SVN-checkout step of the build process with a baseURL= argument to provide the common portion of the SVN URL, and add a defaultBranch= argument to point to the trunk. Each Build is done for a specific branch, and the SVN checkout step just appends the branch name to the baseURL to figure out what to pass to 'svn co %s' Assuming the ChangeSource is providing branch information properly, this will result in any change to the trunk causing a trunk build, and any change to the 2.4 branch causing a 2.4 build. Your master.cfg file will probably want to have some of the following elements: ---(Continue reading)BEGIN--- from buildbot.changes.pb import PBChangeSource c['sources'] = PBChangeSource() # N.B.: don't set prefix=
RSS Feed