[Buildbot-commits] buildbot/docs buildbot.texinfo,1.89,1.90

Brian Warner warner at users.sourceforge.net
Wed Dec 6 08:40:11 UTC 2006

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

Modified Files:
Log Message:
[project @ document some of the other FileUpload/FileDownload arguments]

Original author: warner at lothar.com
Date: 2006-12-06 08:38:12

Index: buildbot.texinfo
RCS file: /cvsroot/buildbot/buildbot/docs/buildbot.texinfo,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- buildbot.texinfo	6 Dec 2006 08:15:42 -0000	1.89
+++ buildbot.texinfo	6 Dec 2006 08:40:09 -0000	1.90
@@ -4149,7 +4149,26 @@
 f.addStep(ShellCommand, command=["make", "config"])
 @end example
- at c TODO: document other parameters
+Like @code{FileUpload}, the @code{mastersrc=} argument is interpreted
+relative to the buildmaster's base directory, and the
+ at code{slavedest=} argument is relative to the builder's working
+directory. If the buildslave is running in @file{~buildslave}, and the
+builder's ``builddir'' is something like @file{tests-i386}, then the
+workdir is going to be @file{~buildslave/tests-i386/build}, and a
+ at code{slavedest=} of @file{foo/bar.html} will get put in
+ at file{~buildslave/tests-i386/build/foo/bar.html}. Remember that
+neither of these commands will create missing directories for you.
+ at subheading Other Parameters
+The @code{maxsize=} argument lets you set a maximum size for the file
+to be transferred. This may help to avoid surprises: transferring a
+100MB coredump when you were expecting to move a 10kB status file
+might take an awfully long time. The @code{blocksize=} argument
+controls how the file is sent over the network: larger blocksizes are
+slightly more efficient but also consume more memory on each end, and
+there is a hard-coded limit of about 640kB.
 @node Writing New BuildSteps,  , Transferring Files, Build Steps

More information about the Commits mailing list