[Buildbot-commits] buildbot/buildbot/slave bot.py,1.9,1.10 commands.py,1.21,1.22

[Brian Warner]

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

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

merge doc updates [org.apestaart at thomas/buildbot--doc--0--patch-6]

Merge epydoc changes from Thomas, add some hacks of my own. No code
changes to the buildbot itself, although I hacked docs/epyrun a bit.


Index: bot.py
===================================================================
RCS file: /cvsroot/buildbot/buildbot/buildbot/slave/bot.py,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- bot.py	11 Apr 2005 19:30:28 -0000	1.9
+++ bot.py	18 Apr 2005 00:26:56 -0000	1.10
@@ -114,8 +114,13 @@
         log.msg("startBuild")
 
     def remote_startCommand(self, stepref, stepId, command, args):
-        """This is called multiple times by various master-side BuildSteps,
-        to start various commands that actually do the build."""
+        """
+        This gets invoked by L{buildbot.process.step.RemoteCommand.start}, as
+        part of various master-side BuildSteps, to start various commands
+        that actually do the build. I return nothing. Eventually I will call
+        .commandComplete() to notify the master-side RemoteCommand that I'm
+        done.
+        """
 
         self.activity()
 
@@ -162,13 +167,14 @@
         self.command.interrupt() # die!
         self.command = None # forget you!
 
-
     # sendUpdate is invoked by the Commands we spawn
     def sendUpdate(self, data):
-        """This sends the status update to the master-side BuildStep object,
-        giving it a sequence number in the process. It adds the update to
-        a queue, and asks the master to acknowledge the update so it can be
-        removed from that queue."""
+        """This sends the status update to the master-side
+        L{buildbot.process.step.RemoteCommand} object, giving it a sequence
+        number in the process. It adds the update to a queue, and asks the
+        master to acknowledge the update so it can be removed from that
+        queue."""
+
         if not self.running:
             # .running comes from service.Service, and says whether the
             # service is running or not. If we aren't running, don't send any

Index: commands.py
===================================================================
RCS file: /cvsroot/buildbot/buildbot/buildbot/slave/commands.py,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- commands.py	11 Apr 2005 19:30:28 -0000	1.21
+++ commands.py	18 Apr 2005 00:26:56 -0000	1.22
@@ -422,6 +422,11 @@
 
 
 class DummyCommand(Command):
+    """
+    I am a dummy no-op command that by default takes 5 seconds to complete.
+    See L{buildbot.process.step.RemoteDummy}
+    """
+    
     def start(self):
         self.d = defer.Deferred()
         log.msg("  starting dummy command [%s]" % self.stepId)