[Buildbot-commits] buildbot/docs buildbot.texinfo,1.113,1.114

[Brian Warner]

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

Modified Files:
	buildbot.texinfo 
Log Message:
[project @ document the branch= query arg]

Original author: warner at lothar.com
Date: 2007-08-02 00:26:28+00:00

Index: buildbot.texinfo
===================================================================
RCS file: /cvsroot/buildbot/buildbot/docs/buildbot.texinfo,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- buildbot.texinfo	1 Aug 2007 22:27:29 -0000	1.113
+++ buildbot.texinfo	2 Aug 2007 00:27:09 -0000	1.114
@@ -5961,7 +5961,7 @@
 contain links to them. Of course other project web pages can contain
 links to these buildbot pages as well.
 
-Each page can be modified by adding query arguments to the URL. For
+Many pages can be modified by adding query arguments to the URL. For
 example, a page which shows the results of the most recent build
 normally does this for all builders at once. But by appending
 ``?builder=i386'' to the end of the URL, the page will show only the
@@ -5971,6 +5971,19 @@
 ampersands, a URL that ends in ``?builder=i386&builder=ppc'' would
 show builds for just those two Builders.
 
+The @code{branch=} query argument can be used on some pages. This
+filters the information displayed by that page down to only the builds
+or changes which involved the given branch. Multiple @code{branch=}
+arguments can be used to examine multiple branches at once (so
+appending @code{?branch=foo&branch=bar} to the URL will show builds
+involving either branch). No @code{branch=} arguments means to show
+builds and changes for all branches.
+
+Note that branch-handling still needs to be cleaned up: in particular
+there is currently no way to refer to the default (or ``trunk'')
+branch using @code{branch=} arguments. This will be improved in a
+future release.
+
 Some pages may include the Builder name or the build number in the
 main part of the URL itself. For example, a page that describes Build
 #7 of the ``i386'' builder would live at @file{/builders/i386/builds/7}.
@@ -5989,7 +6002,9 @@
 all builders. It is the same display used by the Waterfall display.
 
 By adding one or more ``builder='' query arguments, the Waterfall is
-restricted to only showing information about the given Builders.
+restricted to only showing information about the given Builders. By
+adding one or more ``branch='' query arguments, the display is
+restricted to showing information about the given branches.
 
 A 'show_events=true' query argument causes the display to include
 non-Build events, like slaves attaching and detaching, as well as
@@ -6080,7 +6095,7 @@
 @item /xmlrpc
 
 This runs an XML-RPC server which can be used to query status
-information about various builds. See @xref{XMLRPC server} for more
+information about various builds. See @ref{XMLRPC server} for more
 details.
 
 @end table