[Repoze-checkins] r659 - www/trunk/blog.repoze.org/entries

[root at laguna.palladion.com]

Author: root
Date: Mon Feb  4 21:58:26 2008
New Revision: 659

Log:
Formatting fixes.

Modified:
   www/trunk/blog.repoze.org/entries/continuous_integration_via_buildbot-20080214.txt

Modified: www/trunk/blog.repoze.org/entries/continuous_integration_via_buildbot-20080214.txt
==============================================================================
--- www/trunk/blog.repoze.org/entries/continuous_integration_via_buildbot-20080214.txt	(original)
+++ www/trunk/blog.repoze.org/entries/continuous_integration_via_buildbot-20080214.txt	Mon Feb  4 21:58:26 2008
@@ -1,8 +1,8 @@
 Continuous Integration via Buildbot
 #label general
-<h2> Or, How I learned to stop worrying ... </h2>
+<h4> Or, How I learned to stop worrying ... </h4>
 
-<h3> Rationale </h3>
+<h5> Rationale </h5>
 
 <p> After running across a portability / build problem with a distutils
     package recently, I realized that the testing we are doing for Repoze
@@ -14,7 +14,7 @@
     <a href="http://buildbot.sourceforge.net">Buildbot</a>, the same tool
     used to run the Zope unit tests.</p>
 
-<h3> Setting Up the Master </h3>
+<h5> Setting Up the Master </h5>
 
 <p> First, I decided to set up the buildbot "master", running on the
     repoze.org server.  This process tracks all pending changes which
@@ -82,7 +82,7 @@
   $ bin/buildbot start var/masters/repoze
 </pre>
 
-<h3> Setting up a "buildslave"</h3>
+<h5> Setting up a "buildslave"</h5>
 
 <p> Next, I could work on setting up the first "buildslave":<p>
 
@@ -126,7 +126,7 @@
     which is great, as my laptop may or may not be online when a change
     is triggered.</p>
 
-<h3> Conclusions </h3>
+<h5> Conclusions </h5>
 
 <p> First, the product does what it is designed for:  it handles the complex
     process of dispatching asynchronous builds to the various platforms