Thorsten Scherler wrote:
[OT] I love the ASF spirit that some people not only care for specific
projects but rather for the whole foundation. Thx.
El jue, 12-01-2006 a las 10:09 +0000, Ross Gardler escribió:
Thorsten Scherler wrote:
last night I finished the update of our documentation that is working
with >0.7. I fixed all error that I had the other day, if you have
forrest 0.7 or 0.8-dev (like I) the docu HEAD should build without
errors.
Next thing on my todo list is to set up a forrest bot on our zone that
the documentation are generated and deployed automatically.
You cannot deploy the docs automatically due to security restrictions in
the ASF. What you can do is deploy to a staging server.
Hmm, ok. I thought in forrest we are doing this.
No, we are deploying to the zone so that we can do quality checks,
however, the deployment to the lives server (or rather the staging serer
before the live server is done manually).
Bummer. ...but I can
have an additional cron job that is doing an svn up for lenya.apache.org
from the staging server, or?
Since the staging server is SVN based the Forrestbot can deploy directly
to there and then the live site will get updated in the usual update
cycle. We'll talk you though it on the Forrest list.
The main
hurdle is our changes.xml.
Since we are building it from svn log it is growing too much and it
takes far to long to
a) checkout log.xml
b) deploy changes.xml
c) request changes.html
This sounds like a manual process, is it?
Yeah. :(
Why not add functionality to the projectInfo plugin in Forrest to handle
your log.xml format, this is what Forrest does with its own status.xml file.
...
...and yes, we should try to add this functionality to the projectInfo
plugin.
How do we get around the saxon8 requirements?
Depends on whether the stylesheet needs saxon8 or it just happens to be
that Saxon8 is the one suggested. I'm sure we can create an XSL that
will work within Forrest.
How can we generate the
log.xml only for certain revision and not every time for the whole lot?
How can we split changes.html in smaller pieces?
The forrestbot has the ability to run a script before building the site,
just write a script that pulls the relevant revision range from SVN
before execution. More on the Forrest dev list.
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
