incubator-easyant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <jeanlouis.boud...@gmail.com>
Subject Re: Website
Date Wed, 09 Mar 2011 11:05:36 GMT
Ooops i forgot the link

[1] https://issues.apache.org/jira/browse/INFRA-3488

2011/3/9 Jean-Louis Boudart <jeanlouis.boudart@gmail.com>

> It seems that we can't have a staging website [1] except if we use Apache
> CMS.
>
> Now comes a few questions:
>
>    - As we haven't really started our website, should we follow our
>    original idea and use xooki to generate our website ?
>    - Do we really need a staging website ? or can we live with only
>     production branch published "in live" ?
>
>
>
> 2011/2/28 Jean-Louis Boudart <jeanlouis.boudart@gmail.com>
>
> Looks good for me. I also think it would be great to have a staging
>> website.
>>
>> The process seems workable enough and can be handled by an easyant build
>> (playing with scm-svn, xooki plugin).
>> We can imagine having something like this  :
>>
>>    - easyant publish-local : would generate local website
>>    - easyant publish-shared : would generate the staging website and
>>    publish it
>>    - easyant release : would generate the production website
>>
>> I created an issue for this (
>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a draft
>> there :p
>>
>>
>>
>> Le 28 février 2011 11:34, Nicolas Lalevée <nicolas.lalevee@hibnet.org> a
>> écrit :
>>
>> Hi guys,
>>>
>>> (most of this email is quite a duplicate of the one I have done on
>>> ant-dev)
>>>
>>> Finally I looked myself into how the Apache CMS works.
>>> So basically it is about having somewhere in svn the sources of the
>>> website in markdown format. 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 staging.apache.org. 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 www.apache.org.
>>>
>>> For thoses who don't know, svnpubsub is a tool developed by the ASF infra
>>> in order to have svn changed quite quickly and efficiently retrieved. The
>>> ASF infra is promoting it for website publishing.
>>>
>>> For our needs, I think it would be great to have both a staging and a
>>> production branches, so there would also be a
>>> http://incubator.staging.apache.org/easyant/.
>>>
>>> About having a buildbot to build the website, I don't think it is
>>> possible with xooki, as the current build around xooki is not able to make
>>> the distinction between a change in the template and a change in a source.
>>> So the build doesn't know wether to build the changed files or the entire
>>> website. As the xooki generation is quite slow, if there is a lot of page
>>> like in the Ivy site, it can takes ages.
>>>
>>> But I think this is still workable with xooki. So what I suggest is
>>> having the following svn layout:
>>> * incubator/easyant/site/sources
>>> * incubator/easyant/site/staging
>>> * incubator/easyant/site/production
>>> And the process will be:
>>> * edit the xooki files in "sources"
>>> * locally launch a build so that "staging" get populated (and we are the
>>> smart ones which will either launch a build for an update or a launch for a
>>> complete rebuild)
>>> * commit the generated files in "staging"
>>> * "staging" get automatically deployed on
>>> http://incubator.staging.apache.org/easyant/ via svnpubsub
>>> * promoting to live will be about svn merging the "staging" into the
>>> "production" branch
>>> * the merge commit in "production" will be automatically be deployed on
>>> http://incubator.apache.org/easyant/ via svnpubsub
>>>
>>> WDYT ?
>>>
>>> Nicolas
>>>
>>>
>>
>>
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Project Lead http://www.easyant.org
>>
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
>



-- 
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message