[Buildbot-commits] buildbot/docs buildbot.texinfo,1.17,1.18

[Brian Warner]

Update of /cvsroot/buildbot/buildbot/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29870/docs

Modified Files:
	buildbot.texinfo 
Log Message:
Revision: arch at buildbot.sf.net--2004/buildbot--dev--0--patch-281
Creator:  Brian Warner <warner at monolith.lothar.com>

add --builder control to 'buildbot try'

	* docs/buildbot.texinfo (try): document both --builder and
	'try_builders' in .buildbot/options
	* buildbot/scripts/runner.py (TryOptions): add --builder,
	accumulate the values into opts['builders']
	* buildbot/scripts/tryclient.py (Try.__init__): set builders
	* buildbot/test/test_runner.py (Try): add some quick tests to make
	sure 'buildbot try --options' and .buildbot/options get parsed
	* buildbot/test/test_scheduler.py (Scheduling.testTryUserpass):
	use --builder control

--This line, and those below, will be ignored--
Files to commit:
   <can't compute list>

This list might be incomplete or outdated if editing the log
message was not invoked from an up-to-date changes buffer!


Index: buildbot.texinfo
===================================================================
RCS file: /cvsroot/buildbot/buildbot/docs/buildbot.texinfo,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- buildbot.texinfo	11 Aug 2005 08:22:17 -0000	1.17
+++ buildbot.texinfo	11 Aug 2005 20:21:31 -0000	1.18
@@ -3767,9 +3767,31 @@
 above. The trydir can be relative to the user's home directory, but
 most of the time you will use an explicit path like
 @file{~buildbot/project/trydir}. These arguments can be provided in
- at file{.buildbot.options} as @code{try_host}, @code{try_username},
+ at file{.buildbot/options} as @code{try_host}, @code{try_username},
 @code{try_password}, and @code{try_dir}.
 
+ at heading choosing the Builders
+
+A trial build is performed on multiple Builders at the same time, and
+the developer gets to choose which Builders are used (limited to a set
+selected by the buildmaster admin with the TryScheduler's
+ at code{builderNames=} argument). The set you choose will depend upon
+what your goals are: if you are concerned about cross-platform
+compatibility, you should use multiple Builders, one from each
+platform of interest. You might use just one builder if that platform
+has libraries or other facilities that allow better test coverage than
+what you can accomplish on your own machine, or faster test runs.
+
+The set of Builders to use can be specified with multiple
+ at option{--builder} arguments on the command line. It can also be
+specified with a single @code{try_builders} option in
+ at file{.buildbot/options} that uses a list of strings to specify all
+the Builder names:
+
+ at example
+try_builders = ["full-OSX", "full-win32", "full-linux"]
+ at end example
+
 @heading specifying the VC system
 
 The @command{try} command also needs to know how to take the