You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Olivier Lamy <ol...@apache.org> on 2012/09/03 09:08:48 UTC
Re: Moving site to svnpub
So that's fast to deploy web sites now.
But the main issue when you want to update main site is to
checkout/update the full content locally (including docs subsites
redback etc...) : OUCH !
I wonder about using a mix solution as we try in maven. The main site
will deployed using a kind of cms (a buildbot job do mvn site and then
publish the site: we need only to go to cms and click on publish).
WDYT ?
2012/8/29 Olivier Lamy <ol...@apache.org>:
> done.
> Now site deployment is really fast :-)
>
> 2012/8/29 Deng Ching <oc...@apache.org>:
>> Cool, thanks Olivier! :)
>>
>> On Wed, Aug 29, 2012 at 1:14 AM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> 2012/8/28 Deng Ching <oc...@apache.org>:
>>> > +1
>>> >
>>> > AFAIK, most of our users are using either 1.3.5 of 1.4-M2 so it should
>>> > probably be fine to keep just n & n-1 reference..
>>>
>>> Sure.
>>> So I did the job (sorry for email spamming :-) ).
>>> The svn path is here:
>>> http://svn.apache.org/repos/asf/archiva/site-content/
>>> Most of the content has been imported and pom configured !
>>> I will ask infra to use this for sync live to archiva.a.o
>>>
>>>
>>> >
>>> > Thanks,
>>> > Deng
>>> >
>>> > On Tue, Aug 28, 2012 at 4:47 AM, Olivier Lamy <ol...@apache.org> wrote:
>>> >
>>> >> Hi,
>>> >> I'd like we move our site to svnpub (faster prod live around 2/3
>>> >> minutes after the commit really faster than the rsync :-) ).
>>> >> I have tested that on an other Apache project
>>> >> (http://directmemory.apache.org) with the maven plugin
>>> >> (http://maven.apache.org/sandbox/plugins/maven-scm-publish-plugin/).
>>> >>
>>> >> First I have to import some content from p.a.o.
>>> >> Question are we sure about keep all of those versionned documentation
>>> >> (http://archiva.apache.org/docs/).
>>> >> Having n and n-1 sounds enough for me.
>>> >>
>>> >> WDYT ?
>>> >>
>>> >> Thanks
>>> >> --
>>> >> Olivier Lamy
>>> >> Talend: http://coders.talend.com
>>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> >>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Moving site to svnpub
Posted by Olivier Lamy <ol...@apache.org>.
2012/9/3 Eric Barboni <Er...@irit.fr>:
> Hi,
>
> your mix approach seems lighter for us.
> Does the current process means if we update site-content and change and
> commit there it may be published with no match from the modules site
> sources?
no it will match :-)
For only root site, a build bot agent will run mvn site and commit the
generated content.
The only change (as opposite current situation) is to have to go to
cms and click on publish button to commit the staged site (note we
will have access to a staged/preview site)
Makes sense ?
>
> Eric
>
>
> -----Message d'origine-----
> De : Olivier Lamy [mailto:olamy@apache.org]
> Envoyé : lundi 3 septembre 2012 09:09
> À : dev@archiva.apache.org
> Objet : Re: Moving site to svnpub
>
> So that's fast to deploy web sites now.
> But the main issue when you want to update main site is to checkout/update
> the full content locally (including docs subsites redback etc...) : OUCH !
> I wonder about using a mix solution as we try in maven. The main site will
> deployed using a kind of cms (a buildbot job do mvn site and then publish
> the site: we need only to go to cms and click on publish).
>
> WDYT ?
>
> 2012/8/29 Olivier Lamy <ol...@apache.org>:
>> done.
>> Now site deployment is really fast :-)
>>
>> 2012/8/29 Deng Ching <oc...@apache.org>:
>>> Cool, thanks Olivier! :)
>>>
>>> On Wed, Aug 29, 2012 at 1:14 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> 2012/8/28 Deng Ching <oc...@apache.org>:
>>>> > +1
>>>> >
>>>> > AFAIK, most of our users are using either 1.3.5 of 1.4-M2 so it
>>>> > should probably be fine to keep just n & n-1 reference..
>>>>
>>>> Sure.
>>>> So I did the job (sorry for email spamming :-) ).
>>>> The svn path is here:
>>>> http://svn.apache.org/repos/asf/archiva/site-content/
>>>> Most of the content has been imported and pom configured !
>>>> I will ask infra to use this for sync live to archiva.a.o
>>>>
>>>>
>>>> >
>>>> > Thanks,
>>>> > Deng
>>>> >
>>>> > On Tue, Aug 28, 2012 at 4:47 AM, Olivier Lamy <ol...@apache.org>
> wrote:
>>>> >
>>>> >> Hi,
>>>> >> I'd like we move our site to svnpub (faster prod live around 2/3
>>>> >> minutes after the commit really faster than the rsync :-) ).
>>>> >> I have tested that on an other Apache project
>>>> >> (http://directmemory.apache.org) with the maven plugin
>>>> >> (http://maven.apache.org/sandbox/plugins/maven-scm-publish-plugin/).
>>>> >>
>>>> >> First I have to import some content from p.a.o.
>>>> >> Question are we sure about keep all of those versionned
>>>> >> documentation (http://archiva.apache.org/docs/).
>>>> >> Having n and n-1 sounds enough for me.
>>>> >>
>>>> >> WDYT ?
>>>> >>
>>>> >> Thanks
>>>> >> --
>>>> >> Olivier Lamy
>>>> >> Talend: http://coders.talend.com
>>>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>> >>
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
RE: Moving site to svnpub
Posted by Eric Barboni <Er...@irit.fr>.
Hi,
your mix approach seems lighter for us.
Does the current process means if we update site-content and change and
commit there it may be published with no match from the modules site
sources?
Eric
-----Message d'origine-----
De : Olivier Lamy [mailto:olamy@apache.org]
Envoyé : lundi 3 septembre 2012 09:09
À : dev@archiva.apache.org
Objet : Re: Moving site to svnpub
So that's fast to deploy web sites now.
But the main issue when you want to update main site is to checkout/update
the full content locally (including docs subsites redback etc...) : OUCH !
I wonder about using a mix solution as we try in maven. The main site will
deployed using a kind of cms (a buildbot job do mvn site and then publish
the site: we need only to go to cms and click on publish).
WDYT ?
2012/8/29 Olivier Lamy <ol...@apache.org>:
> done.
> Now site deployment is really fast :-)
>
> 2012/8/29 Deng Ching <oc...@apache.org>:
>> Cool, thanks Olivier! :)
>>
>> On Wed, Aug 29, 2012 at 1:14 AM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> 2012/8/28 Deng Ching <oc...@apache.org>:
>>> > +1
>>> >
>>> > AFAIK, most of our users are using either 1.3.5 of 1.4-M2 so it
>>> > should probably be fine to keep just n & n-1 reference..
>>>
>>> Sure.
>>> So I did the job (sorry for email spamming :-) ).
>>> The svn path is here:
>>> http://svn.apache.org/repos/asf/archiva/site-content/
>>> Most of the content has been imported and pom configured !
>>> I will ask infra to use this for sync live to archiva.a.o
>>>
>>>
>>> >
>>> > Thanks,
>>> > Deng
>>> >
>>> > On Tue, Aug 28, 2012 at 4:47 AM, Olivier Lamy <ol...@apache.org>
wrote:
>>> >
>>> >> Hi,
>>> >> I'd like we move our site to svnpub (faster prod live around 2/3
>>> >> minutes after the commit really faster than the rsync :-) ).
>>> >> I have tested that on an other Apache project
>>> >> (http://directmemory.apache.org) with the maven plugin
>>> >> (http://maven.apache.org/sandbox/plugins/maven-scm-publish-plugin/).
>>> >>
>>> >> First I have to import some content from p.a.o.
>>> >> Question are we sure about keep all of those versionned
>>> >> documentation (http://archiva.apache.org/docs/).
>>> >> Having n and n-1 sounds enough for me.
>>> >>
>>> >> WDYT ?
>>> >>
>>> >> Thanks
>>> >> --
>>> >> Olivier Lamy
>>> >> Talend: http://coders.talend.com
>>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> >>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy