[Buildbot-commits] site manual-CVS.html,1.2,1.3

[Brian Warner]

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

Modified Files:
	manual-CVS.html 
Log Message:
more Try stuff

Index: manual-CVS.html
===================================================================
RCS file: /cvsroot/buildbot/site/manual-CVS.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- manual-CVS.html	11 Aug 2005 19:48:49 -0000	1.2
+++ manual-CVS.html	31 Aug 2005 07:21:23 -0000	1.3
@@ -4211,6 +4211,13 @@
 <span class="file">.buildbot/options</span> as <code>try_host</code>, <code>try_username</code>,
 <code>try_password</code>, and <code>try_dir</code>.
 
+   <p>In addition, the SSH approach needs to connect to a PBListener status
+port, so it can retrieve and report the results of the build (the PB
+approach uses the existing connection to retrieve status information,
+so this step is not necessary). This requires a <span class="option">--master</span>
+argument, or a <code>masterstatus</code> entry in <span class="file">.buildbot/options</span>,
+in the form of a HOSTNAME:PORT string.
+
 <h3 class="heading">choosing the Builders</h3>
 
 <p>A trial build is performed on multiple Builders at the same time, and
@@ -4271,6 +4278,16 @@
 <span class="option">--try-topfile</span> and <span class="option">--try-topdir</span> arguments will be
 ignored.
 
+<h3 class="heading">determining the branch name</h3>
+
+<p>Some VC systems record the branch information in a way that “try”
+can locate it, in particular Arch (both <span class="command">tla</span> and
+<span class="command">baz</span>). For the others, if you are using something other than
+the default branch, you will have to tell the buildbot which branch
+your tree is using. You can do this with either the <span class="option">--branch</span>
+argument, or a <span class="option">try_branch</span> entry in the
+<span class="file">.buildbot/options</span> file.
+
 <h3 class="heading">determining the revision and patch</h3>
 
 <p>Each VC system has a separate approach for determining the tree's base
@@ -4367,8 +4384,14 @@
 that use numeric transaction numbers (like Subversion).
 
      <br><dt><code>--revision</code><dd>This provides a (string) revision specifier, for VC systems that use
-strings (Arch would use something like patch-42, Darcs would use the
-patch name, etc).
+strings (Arch would use something like patch-42 etc).
+
+     <br><dt><code>--revision_file</code><dd>This provides a filename which will be opened and the contents used as
+the revision specifier. This is specifically for Darcs, which uses the
+output of <span class="command">darcs changes --context</span> as a revision specifier. 
+This context file can be a couple of kilobytes long, spanning a couple
+lines per patch, and would be a hassle to pass as a command-line
+argument.
 
      <br><dt><code>--comments</code><dd>This provides the change comments as a single argument. You may want
 to use <span class="option">--logfile</span> instead.