Gennadiy Rozental wrote:
The rationale behind the "timely" goal is that developers will benefit tremendously from faster feedback, both for HEAD and active branches. Automating the feedback will free developers from having to track what is happening on many different platforms.
Will it allow to test against non-HEAD branches? How would it work?
Perhaps the best response to the non-HEAD question is to post the configuration for the bot I'm currently running: config['builders'].append( { "name" : "RSI-SoL-Full", "slavename" : "RSI-SoL", "builddir" : "rsi_sol_full", "factory" : Boost_BuildFactory( action('cvs' ,root = ':ext:grafik@cvs.sourceforge.net:/cvsroot/boost' ,module = 'boost' ,files = [] ,haltOnFailure = True), action('bjam_build' ,haltOnFailure = True), action('btest_all' ,toolset = 'gcc-3_4_3-linux-i686-release' ,build = 'release' ,env = { 'PYTHON_ROOT': '/usr', 'PYTHON_VERSION': '2.3' } ,flunkOnFailure = False, warnOnFailure = True), action('test_tools_build' ,toolset = 'gcc' ,haltOnFailure = True), action('process_jam_log' ,haltOnFailure = True), action('collect_results' ,runner = 'RSI-SoL' ,haltOnFailure = True), action('publish_results' ,runner = 'RSI-SoL' ,publish_location = 'ftp://fx.meta-comm.com/boost-regression' ,haltOnFailure = True), workdir = 'boost', branch = 'HEAD', source_type = 'CVS' ) } ) As you can see testing on other branches is changing the "branch = HEAD" option above. Not that I've tried this yet :-) So it's likely to have initial problems. For those curious I added the code to the sandbox CVS under boost-sandbox/tools/boostbot/. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org