Yeah, just seems like the svn repo can be automatically pushed to from multiple sources to update the overall site content (javadoc, markdown processed stuff, test results, etc).
On Tue, May 7, 2013 at 11:40 AM, Adrian Cole <[email protected]>wrote: > well github pages main value is autopublishing to a CNAME. Seems the case > that ASF already has means to do so, or similar. I think we should keep > this as a best-of and not go through hoops solely to use github infra > > +1 keep jekyll and any other good parts of the current process (like > buildhive jekyll checks). > > my 2p > -A > > On Tue, May 7, 2013 at 11:29 AM, David Nalley <[email protected]> wrote: > > > On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <[email protected]> > > wrote: > > > Are there any specific requirements with regard to an audit trail for > > > changes to the site? > > > > > > Do we need to be able to show commit logs etc. too, or is it OK to have > > > those in GitHub and regard the Apache site as the hosting location for > > the > > > Jekyll-generated HTML, which would be (over-)written on every merge..? > > > > > > +1 on the idea of running this via Jekyll. Could/should we be using > > Apache > > > CI infrastructure to do this, or is CloudBees OK (for now)? > > > > > > ap > > > > Website requires svn (long story, but basically, svnpubsub is > > required). Jekyll should be fine as a build tool (Olamy or Suresh, > > feel free to correct me) - so you could theoretically do a svn->git > > replication, but no real way of escaping svn for the website. > > > > --David > > >
