forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r1502940 - in /forrest/trunk/site-author/content/xdocs: howto-forrestbot-svn.xml procedures/How_to_publish_docs.xml
Date Sun, 14 Jul 2013 05:43:29 GMT
Author: crossley
Date: Sun Jul 14 05:43:29 2013
New Revision: 1502940

URL: http://svn.apache.org/r1502940
Log:
We use svnpubsub now.

Modified:
    forrest/trunk/site-author/content/xdocs/howto-forrestbot-svn.xml
    forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml

Modified: forrest/trunk/site-author/content/xdocs/howto-forrestbot-svn.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/howto-forrestbot-svn.xml?rev=1502940&r1=1502939&r2=1502940&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/howto-forrestbot-svn.xml (original)
+++ forrest/trunk/site-author/content/xdocs/howto-forrestbot-svn.xml Sun Jul 14 05:43:29 2013
@@ -61,7 +61,10 @@
         Our source documents are managed in the project's Subversion (SVN) version control
system. Each committer has a local SVN working copy on their office computer. We can prepare
source changes and review them with 'forrest run' and 'forrest validate-xdocs'. When satisfied
we 'svn commit' those changes. Our Forrestbot uses the "getsrc.local" workstage to retrieve
the sources from the local svn checkout.
       </p>
       <p>
-        The generated static documents which form the website are also stored in SVN. So
our Forrestbot uses the "deploy.svn" workstage to deploy the generated documents. To publish
the website, a regular cron job on the apache.org server automatically does 'svn update' in
the website's document space. Elegant.
+        The generated static documents which form the website are also stored in SVN. So
our Forrestbot uses the "deploy.svn" workstage to deploy the generated documents.
+        The svnpubsub system automatically kicks in to do the final publish step
+        (see <a href="http://www.apache.org/dev/project-site#intro">explanation</a>).
+        Elegant.
       </p>
       <p>
         That is what we call a "local forrestbot". Each committer can conduct

Modified: forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml?rev=1502940&r1=1502939&r2=1502940&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/How_to_publish_docs.xml Sun Jul 14
05:43:29 2013
@@ -58,12 +58,9 @@ forrest -f publish.xml deploy</source>
         This builds the documentation locally then deploys it by committing it
         to the
         <a href="http://svn.apache.org/repos/asf/forrest/site">forrest/site
-        SVN</a>. Then a cronjob on the server will automatically publish it.
-        However, if quicker turnaround is required, then do this:
+        SVN</a>.
+        The svnpubsub system automatically kicks in to do the final publish step.
       </p>
-      <source>ssh people.apache.org
-cd /www/forrest.apache.org
-svn update</source>
       <p>
         See more detailed <a href="site:forrestbot-svn">explanation</a> of this
         procedure.



Mime
View raw message