[Buildbot-commits] buildbot ChangeLog,1.795,1.796 NEWS,1.60,1.61

Brian Warner warner at users.sourceforge.net
Wed Dec 6 09:17:33 UTC 2006

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

Modified Files:
	ChangeLog NEWS 
Log Message:
[project @ more NEWS items]

Original author: warner at lothar.com
Date: 2006-12-06 09:15:41

Index: ChangeLog
RCS file: /cvsroot/buildbot/buildbot/ChangeLog,v
retrieving revision 1.795
retrieving revision 1.796
diff -u -d -r1.795 -r1.796
--- ChangeLog	6 Dec 2006 08:51:23 -0000	1.795
+++ ChangeLog	6 Dec 2006 09:17:31 -0000	1.796
@@ -1,5 +1,7 @@
 2006-12-06  Brian Warner  <warner at lothar.com>
+	* NEWS: update with items for the next release
 	* docs/buildbot.texinfo (Adding LogObservers): add a somewhat
 	whimsical example pulled from a punch-drunk email I sent out late
 	one night.

Index: NEWS
RCS file: /cvsroot/buildbot/buildbot/NEWS,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- NEWS	19 Nov 2006 20:22:20 -0000	1.60
+++ NEWS	6 Dec 2006 09:17:31 -0000	1.61
@@ -19,6 +19,29 @@
 ** new features
+*** reconfiguring a Builder no longer causes a disconnect/reconnect cycle
+This means that sending SIGHUP to the master or running 'buildbot reconfig
+MASTERDIR' command no longer interrupts any current builds, nor does it lose
+pending builds like it did before. This involved a fairly substantial
+refactoring of the various internal BotPerspective/BotMaster/Builder classes.
+Note that reconfiguring Schedulers still loses any Changes that were waiting
+for the tree to become stable: hopefully this will be fixed in the next
+*** 'buildbot start/restart/reconfig' now show logs until startup is complete
+These commands now have additional code to follow twistd.log and display all
+the lines that are emitted from the beginning of the start/reconfig action
+until it has completed. This gives you a chance to see any problems detected
+in the config file without needing to manually look in twistd.log or use
+another shell to 'tail -f' it. This also makes it clear which config file is
+being used. This functionality is not available under windows.
+In addition, if any problems are detected during 'start' or 'restart' (but
+not reconfig), the 'buildbot *' command will terminate with a non-zero exit
+status, making it easier to use in scripts. Closes SF#1517975.
 *** Locks now take maxCount=N to allow multiple simultaneous owners
 This allows Locks to be non-exclusive but still limit concurrency. Thanks to
@@ -35,7 +58,10 @@
 buildbot.steps.python.PyFlakes will run the simple 'pyflakes' static analysis
 tool and parse the results to tell you about undefined names, unused imports,
+etc. You'll need to tell it how to run pyflakes, usually with something like
+command=["pyflakes", "src/packagedir"] or the like. The default command is
+"make pyflakes", which assumes that you have a suitable target in your
+top-level Makefile.
 *** Monotone support
@@ -102,7 +128,7 @@
 Earlier versions of buildbot didn't explicitly close any logfiles= file
 handles when the build finished. On windows (where you cannot delete a file
-that someone is reading), this could cause the next build to fail as the
+that someone else is reading), this could cause the next build to fail as the
 source checkout step was unable to delete the old working directory. This has
 been fixed. Closes SF#1568415.
@@ -112,6 +138,12 @@
 EOF, the result was that logfiles= sometimes didn't work. Thanks to Mark Rowe
 for the patch.
+** other changes
+The 'buildbot sighup MASTERDIR' command has been replaced with 'buildbot
+reconfig MASTERDIR', since that seems to be a slightly more meaningful name.
+The 'sighup' form will remain as an alias.
 * Release 0.7.4 (23 Aug 2006)

More information about the Commits mailing list