ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Website and svnpubsub
Date Mon, 28 Feb 2011 16:08:53 GMT
On 2011-02-28, Nicolas Lalevée wrote:

> Finally I looked myself into how the Apache CMS works and how could
> our website edition and publication could be similar or integrated.

Great, thanks.

> So basically it is about having somewhere in svn the sources of the
> website. A buildbot job then takes care of building the html files and
> commit them into a "staging" branch. The staging branch is published
> via svnpubsub to Then we can trigger a merge of
> the staging branch into a production one. Another buildbot build the
> html file and again a svnpubsub push it to

Is "trigger a merge" something one does while looking at the staging
side or a manula "svn merge"?

> I think it would be great to also have both a staging and a production
> branches, so there would also be a

Even though I never missed it, I'm sure a staging area can be useful at

> And about svnpubsub, since we already have the generated content in
> svn, we could use it without worries.

True.  As long as we don't merge things we don't want to publish right
now to the svnpubsub source dir by accident.

> So I suggest that we keep our current local manual build and commit
> until we have smart generation tasks. I also suggest we maintain two
> branches of the site, a staging and a production one. And the
> publication will be automatically done via svnpubsub.

Sounds good.

> If we agree, we'll need new branches. I suggest to maintain Ant and
> Ivy separately so locally we don't have the svn update much before
> generating html files.

> Then the simplest move may be to:
> * make ant/core/trunk/docs/ the staging website for Ant
> * make ant/core/branches/ANT_SITE/docs/ the production website for Ant

Seems to mirror closely what we currently have - or once had, by now
trunk is the production source IIUC.

> Or we can change the layout:
> * ant/site/core/sources
> * ant/site/core/staging
> * ant/site/core/production
> * ant/site/ivy/sources
> * ant/site/ivy/staging
> * ant/site/ivy/production

> But this would mean some tweaks in the current build of ant since the
> website is packaged in the distribution.

Would work for me as well.  Ant could even automate the staging process
from sources since running Anakia should be straight forward inside


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message