Author: sebb
Date: Sat Aug 19 23:23:58 2023
New Revision: 1911786

URL: http://svn.apache.org/viewvc?rev=1911786&view=rev
Log:
Documentation

Added:
    commons/cms-site/trunk/BUILDING.txt   (with props)
Modified:
    commons/cms-site/trunk/commons-site-build.sh

Added: commons/cms-site/trunk/BUILDING.txt
URL: 
http://svn.apache.org/viewvc/commons/cms-site/trunk/BUILDING.txt?rev=1911786&view=auto
==============================================================================
--- commons/cms-site/trunk/BUILDING.txt (added)
+++ commons/cms-site/trunk/BUILDING.txt Sat Aug 19 23:23:58 2023
@@ -0,0 +1,22 @@
+This parent site is automatically built on commit.
+
+This is done by buildbot at:
+
+https://ci2.apache.org/#/builders/91
+
+The buildbot config file is at:
+
+https://svn.apache.org/repos/infra/infrastructure/buildbot2/projects/commons-parent.py
+
+The output is committed to the staging site at:
+
+https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content
+
+Note that the staging site does not contain any of the components (proper/ 
dormant/ sandbox/)
+These are published directly to the production site under (e.g.):
+
+https://svn.apache.org/repos/infra/websites/production/commons/content/proper/
+
+The parent site needs to be merged into the production site.
+This is currently a manual process using commons-site-publish.sh
+

Propchange: commons/cms-site/trunk/BUILDING.txt
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: commons/cms-site/trunk/commons-site-build.sh
URL: 
http://svn.apache.org/viewvc/commons/cms-site/trunk/commons-site-build.sh?rev=1911786&r1=1911785&r2=1911786&view=diff
==============================================================================
--- commons/cms-site/trunk/commons-site-build.sh (original)
+++ commons/cms-site/trunk/commons-site-build.sh Sat Aug 19 23:23:58 2023
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 
-# replacement for buildbot which does not seem to trigger correctly
+# Alternative for buildbot if that does not trigger properly
 
 rm -rf target
 mkdir target


Reply via email to