You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Olivier Lamy <ol...@apache.org> on 2013/05/07 12:31:39 UTC
Web site
Hi,
Where/how/etc.. is generated the content from http://www.jclouds.org ?
The goal is to have it at jclouds.incubator.apache.org.
Let me know and I can work on that.
Cheers,
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Adrian Cole <ad...@gmail.com>.
This site is rendered via jekyll (github pages).
Here's the contents of our buildhive job:
gem install jekyll rdiscount --no-rdoc --no-ri --conservative --user-install
$(find ~/.gem/ -iname jekyll | grep bin | sort -r | head -n 1) --pygments
--no-lsi --safe
To retain the current setup, it is possible the following would work:
1. add a CNAME dns record for jclouds.incubator.apache.org ->
jclouds.github.io (INFRA)
2. update the jclouds.github.com repository CNAME file to
jclouds.incubator.apache.org
3. setup a web site redirect of www.jclouds.org to
jclouds.incubator.apache.org
https://help.github.com/articles/setting-up-a-custom-domain-with-pages
we could migrate the repo to ASF before or after this change I think, but
we should validate if github pages publishing works on remote forks.
-A
On Tue, May 7, 2013 at 5:59 AM, David Nalley <da...@gnsa.us> wrote:
> On Tue, May 7, 2013 at 6:31 AM, Olivier Lamy <ol...@apache.org> wrote:
> > Hi,
> > Where/how/etc.. is generated the content from http://www.jclouds.org ?
> > The goal is to have it at jclouds.incubator.apache.org.
> >
> > Let me know and I can work on that.
> >
>
> https://github.com/jclouds/jclouds.github.com
>
> (incidentally, this is a repo I did not migrate to git, despite it
> being in the proposal as being part of the donation.)
>
> --David
>
Re: Web site
Posted by Matt Stephenson <ma...@mattstep.net>.
It would probably be best to do a git repo for the markup components, and
have the rest in svn. We currently overload the website with tons of
non-markup to take advantage of github pages hosting, we don't need to keep
doing that, so some of the site shouldn't be going through jekyll going
forward, just the markdown/templates.
It would be best now that we have hosting to properly build/host the
javadoc on apache, so navigation is consistently on the same domain.
On Tue, May 7, 2013 at 11:29 AM, David Nalley <da...@gnsa.us> wrote:
> On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <an...@apache.org>
> 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
>
Re: Web site
Posted by Suresh Marru <sm...@apache.org>.
On May 7, 2013, at 2:29 PM, David Nalley <da...@gnsa.us> wrote:
> On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <an...@apache.org> 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.
Thats right. To my knowledge we cannot get away from svn for Apache CMS. I have dealt with CMS for few projects and i will be happy to help with transition, but I am trying to understand the github site of website before I comment on migration. But so far others have good thoughts and I am learning whats out there now in git.
Suresh
>
> --David
Re: Web site
Posted by Adrian Cole <ad...@gmail.com>.
FYI. It should be possible for you to modify CloudBees now that jclouds is
an organization on github. If not, worthwhile contacting support @ to sort
that out.
Cheers,
-A
On Wed, May 8, 2013 at 12:19 AM, Becca Wood <si...@gmail.com> wrote:
> I set the Jenkins job up but Adrian has karma on CloudBees so it is
> currently running on his account. I can set it up to run on my account,
> but it would be ideal to have an account for it to run on that we could all
> have access to in order to work on jobs.
>
>
> On Tue, May 7, 2013 at 11:49 PM, Olivier Lamy <ol...@apache.org> wrote:
>
> > nope Jenkins ASF cannot commit to svn.
> >
> > Usually for other projects I'm involved @asf, I setup that in my
> > private cloudbees instance so no problem for password.
> > Let me know if you think it's a good idea.
> >
> > 2013/5/8 Ignasi <ig...@gmail.com>:
> > > +1. If ASF CI can commit to the svn, that would be the fastest way to
> > > migrate.
> > > El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
> > >
> > >> I'm guessing it would actually be trivial to just port the cloudbees
> job
> > >> Becca setup over to ASF jenkins and just add a step to do an svn
> commit
> > of
> > >> the resulting artifacts.
> > >>
> > >>
> > >> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <
> mattstep@mattstep.net
> > >> >wrote:
> > >>
> > >> > I'm guessing it would actually be trivial to just port the cloudbees
> > job
> > >> > Becca setup over to ASF jenkins and just add a step to do an svn
> > commit
> > >> of
> > >> > the resulting artifacts.
> > >> >
> > >> >
> > >> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org>
> > wrote:
> > >> >
> > >> >> ETA: all is in place.
> > >> >> See http://jclouds.incubator.apache.org :-)
> > >> >> The svn path to populate is here:
> > >> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
> > >> >> Note there are some prerequisite with having incubator logo sample:
> > >> >> http://helix.incubator.apache.org
> > >> >> No time now to work on the infra to publish the real content (I
> will
> > >> >> see later except if someone beat me)
> > >> >>
> > >> >>
> > >> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
> > >> >> >> https://www.apache.org/dev/project-site#intro and make a call
> on
> > if
> > >> >> you
> > >> >> >> would like to port the website to CMS or have the site content
> in
> > >> the
> > >> >> >> current form in git and push the generated html using
> svnpubsub?
> > >> >> >
> > >> >> >
> > >> >> > I'm guessing that for an initial transition Jekyll + svnpubsub
> > would
> > >> >> > certainly be something worth trying out. Which SVN repo (folder)
> > >> should
> > >> >> we
> > >> >> > use for this? Do we need to request that an SVN repo be created
> for
> > >> this
> > >> >> > purpose?
> > >> >> >
> > >> >> > ap
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Olivier Lamy
> > >> >> Ecetera: http://ecetera.com.au
> > >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> > >> >>
> > >> >
> > >> >
> > >>
> >
> >
> >
> > --
> > Olivier Lamy
> > Ecetera: http://ecetera.com.au
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>
Re: Web site
Posted by Andrew Phillips <ap...@qrmedia.com>.
> I set the Jenkins job up but Adrian has karma on CloudBees so it is
> currently running on his account. I can set it up to run on my account,
> but it would be ideal to have an account for it to run on that we could all
> have access to in order to work on jobs.
You (i.e. the "silkysun@gmail.com" CloudBees account) should have
access to the jclouds account on CloudBees now. Let me know if you
need anything more in order to set up the job there!
ap
Re: Web site
Posted by Olivier Lamy <ol...@apache.org>.
probably not complicated :-)
My trouble is to have it in clear in the console output.
2013/5/8 Andrew Phillips <ap...@qrmedia.com>:
>> The issue with a shared cloudbees account is to share your apache
>> password (it's mandatory to commit to the svn path) . And to have it
>> in clear in the console output.
>> Perso I won't :-).
>
>
> I haven't looked at the script yet, but how hard would it be to modify it to
> retrieve the password from somewhere else? We have a private mount in the
> CloudBees account which is, at least, not publicly accessible.
>
> Thanks!
>
> ap
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Andrew Phillips <ap...@qrmedia.com>.
> The issue with a shared cloudbees account is to share your apache
> password (it's mandatory to commit to the svn path) . And to have it
> in clear in the console output.
> Perso I won't :-).
I haven't looked at the script yet, but how hard would it be to modify
it to retrieve the password from somewhere else? We have a private
mount in the CloudBees account which is, at least, not publicly
accessible.
Thanks!
ap
Re: Web site
Posted by Olivier Lamy <ol...@apache.org>.
2013/5/9 Andrew Phillips <ap...@qrmedia.com>:
> Stupid question, Olivier...sorry:
No in fact a good question :-)
I pushed that here https://github.com/jclouds/jclouds.github.com
But do we have the web site git repo @asf git ?
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=summary
doesn't look to be the web site.
Maybe I missed something ? (that's definitely possible :-) )
>
>> script pushed.
>
>
> To where did that script (deploy-site.sh) get pushed? I can't see it in the
> incubator-jclouds Git repo or in
> https://svn.apache.org/repos/asf/incubator/jclouds/.
>
> Thanks!
>
> ap
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Andrew Phillips <ap...@qrmedia.com>.
Stupid question, Olivier...sorry:
> script pushed.
To where did that script (deploy-site.sh) get pushed? I can't see it
in the incubator-jclouds Git repo or in
https://svn.apache.org/repos/asf/incubator/jclouds/.
Thanks!
ap
Re: Web site
Posted by Olivier Lamy <ol...@apache.org>.
script pushed.
To deploy web site to ASF:
* have jekyll installed
* sh ./deploy-site.sh $uid $pwd (with $uid your ASF account $pwd your
ASF password)
I'd like to see Apache incubator in the banner top in pages instead of
bottom :-)
Except someone beat I will see tomorrow evening (aus tz)
--
Olivier
2013/5/8 Olivier Lamy <ol...@apache.org>:
> The issue with a shared cloudbees account is to share your apache
> password (it's mandatory to commit to the svn path) . And to have it
> in clear in the console output.
> Perso I won't :-).
> But I don't see any issue having more than one instance.
>
> So I just commit a first version with Apache Incubator logo (I didn't
> touch yet " The jclouds logo is trademark of jclouds, Inc. " I believe
> transfer is under process )
> I will add a script in the git repo to commit to svn the generated site.
>
> See http://jclouds.incubator.apache.org
> IANAD :-)
>
> 2013/5/8 Becca Wood <si...@gmail.com>:
>> I set the Jenkins job up but Adrian has karma on CloudBees so it is
>> currently running on his account. I can set it up to run on my account,
>> but it would be ideal to have an account for it to run on that we could all
>> have access to in order to work on jobs.
>>
>>
>> On Tue, May 7, 2013 at 11:49 PM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> nope Jenkins ASF cannot commit to svn.
>>>
>>> Usually for other projects I'm involved @asf, I setup that in my
>>> private cloudbees instance so no problem for password.
>>> Let me know if you think it's a good idea.
>>>
>>> 2013/5/8 Ignasi <ig...@gmail.com>:
>>> > +1. If ASF CI can commit to the svn, that would be the fastest way to
>>> > migrate.
>>> > El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
>>> >
>>> >> I'm guessing it would actually be trivial to just port the cloudbees job
>>> >> Becca setup over to ASF jenkins and just add a step to do an svn commit
>>> of
>>> >> the resulting artifacts.
>>> >>
>>> >>
>>> >> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <mattstep@mattstep.net
>>> >> >wrote:
>>> >>
>>> >> > I'm guessing it would actually be trivial to just port the cloudbees
>>> job
>>> >> > Becca setup over to ASF jenkins and just add a step to do an svn
>>> commit
>>> >> of
>>> >> > the resulting artifacts.
>>> >> >
>>> >> >
>>> >> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org>
>>> wrote:
>>> >> >
>>> >> >> ETA: all is in place.
>>> >> >> See http://jclouds.incubator.apache.org :-)
>>> >> >> The svn path to populate is here:
>>> >> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
>>> >> >> Note there are some prerequisite with having incubator logo sample:
>>> >> >> http://helix.incubator.apache.org
>>> >> >> No time now to work on the infra to publish the real content (I will
>>> >> >> see later except if someone beat me)
>>> >> >>
>>> >> >>
>>> >> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
>>> >> >> >> https://www.apache.org/dev/project-site#intro and make a call on
>>> if
>>> >> >> you
>>> >> >> >> would like to port the website to CMS or have the site content in
>>> >> the
>>> >> >> >> current form in git and push the generated html using svnpubsub?
>>> >> >> >
>>> >> >> >
>>> >> >> > I'm guessing that for an initial transition Jekyll + svnpubsub
>>> would
>>> >> >> > certainly be something worth trying out. Which SVN repo (folder)
>>> >> should
>>> >> >> we
>>> >> >> > use for this? Do we need to request that an SVN repo be created for
>>> >> this
>>> >> >> > purpose?
>>> >> >> >
>>> >> >> > ap
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> Olivier Lamy
>>> >> >> Ecetera: http://ecetera.com.au
>>> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Ecetera: http://ecetera.com.au
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Olivier Lamy <ol...@apache.org>.
The issue with a shared cloudbees account is to share your apache
password (it's mandatory to commit to the svn path) . And to have it
in clear in the console output.
Perso I won't :-).
But I don't see any issue having more than one instance.
So I just commit a first version with Apache Incubator logo (I didn't
touch yet " The jclouds logo is trademark of jclouds, Inc. " I believe
transfer is under process )
I will add a script in the git repo to commit to svn the generated site.
See http://jclouds.incubator.apache.org
IANAD :-)
2013/5/8 Becca Wood <si...@gmail.com>:
> I set the Jenkins job up but Adrian has karma on CloudBees so it is
> currently running on his account. I can set it up to run on my account,
> but it would be ideal to have an account for it to run on that we could all
> have access to in order to work on jobs.
>
>
> On Tue, May 7, 2013 at 11:49 PM, Olivier Lamy <ol...@apache.org> wrote:
>
>> nope Jenkins ASF cannot commit to svn.
>>
>> Usually for other projects I'm involved @asf, I setup that in my
>> private cloudbees instance so no problem for password.
>> Let me know if you think it's a good idea.
>>
>> 2013/5/8 Ignasi <ig...@gmail.com>:
>> > +1. If ASF CI can commit to the svn, that would be the fastest way to
>> > migrate.
>> > El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
>> >
>> >> I'm guessing it would actually be trivial to just port the cloudbees job
>> >> Becca setup over to ASF jenkins and just add a step to do an svn commit
>> of
>> >> the resulting artifacts.
>> >>
>> >>
>> >> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <mattstep@mattstep.net
>> >> >wrote:
>> >>
>> >> > I'm guessing it would actually be trivial to just port the cloudbees
>> job
>> >> > Becca setup over to ASF jenkins and just add a step to do an svn
>> commit
>> >> of
>> >> > the resulting artifacts.
>> >> >
>> >> >
>> >> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org>
>> wrote:
>> >> >
>> >> >> ETA: all is in place.
>> >> >> See http://jclouds.incubator.apache.org :-)
>> >> >> The svn path to populate is here:
>> >> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
>> >> >> Note there are some prerequisite with having incubator logo sample:
>> >> >> http://helix.incubator.apache.org
>> >> >> No time now to work on the infra to publish the real content (I will
>> >> >> see later except if someone beat me)
>> >> >>
>> >> >>
>> >> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
>> >> >> >> https://www.apache.org/dev/project-site#intro and make a call on
>> if
>> >> >> you
>> >> >> >> would like to port the website to CMS or have the site content in
>> >> the
>> >> >> >> current form in git and push the generated html using svnpubsub?
>> >> >> >
>> >> >> >
>> >> >> > I'm guessing that for an initial transition Jekyll + svnpubsub
>> would
>> >> >> > certainly be something worth trying out. Which SVN repo (folder)
>> >> should
>> >> >> we
>> >> >> > use for this? Do we need to request that an SVN repo be created for
>> >> this
>> >> >> > purpose?
>> >> >> >
>> >> >> > ap
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Olivier Lamy
>> >> >> Ecetera: http://ecetera.com.au
>> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >> >>
>> >> >
>> >> >
>> >>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Becca Wood <si...@apache.org>.
I set the Jenkins job up but Adrian has karma on CloudBees so it is
currently running on his account. I can set it up to run on my account,
but it would be ideal to have an account for it to run on that we could all
have access to in order to work on jobs.
On Wed, May 8, 2013 at 12:19 AM, Becca Wood <si...@gmail.com> wrote:
> I set the Jenkins job up but Adrian has karma on CloudBees so it is
> currently running on his account. I can set it up to run on my account,
> but it would be ideal to have an account for it to run on that we could all
> have access to in order to work on jobs.
>
>
> On Tue, May 7, 2013 at 11:49 PM, Olivier Lamy <ol...@apache.org> wrote:
>
>> nope Jenkins ASF cannot commit to svn.
>>
>> Usually for other projects I'm involved @asf, I setup that in my
>> private cloudbees instance so no problem for password.
>> Let me know if you think it's a good idea.
>>
>> 2013/5/8 Ignasi <ig...@gmail.com>:
>> > +1. If ASF CI can commit to the svn, that would be the fastest way to
>> > migrate.
>> > El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
>> >
>> >> I'm guessing it would actually be trivial to just port the cloudbees
>> job
>> >> Becca setup over to ASF jenkins and just add a step to do an svn
>> commit of
>> >> the resulting artifacts.
>> >>
>> >>
>> >> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <
>> mattstep@mattstep.net
>> >> >wrote:
>> >>
>> >> > I'm guessing it would actually be trivial to just port the cloudbees
>> job
>> >> > Becca setup over to ASF jenkins and just add a step to do an svn
>> commit
>> >> of
>> >> > the resulting artifacts.
>> >> >
>> >> >
>> >> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org>
>> wrote:
>> >> >
>> >> >> ETA: all is in place.
>> >> >> See http://jclouds.incubator.apache.org :-)
>> >> >> The svn path to populate is here:
>> >> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
>> >> >> Note there are some prerequisite with having incubator logo sample:
>> >> >> http://helix.incubator.apache.org
>> >> >> No time now to work on the infra to publish the real content (I will
>> >> >> see later except if someone beat me)
>> >> >>
>> >> >>
>> >> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
>> >> >> >> https://www.apache.org/dev/project-site#intro and make a call
>> on if
>> >> >> you
>> >> >> >> would like to port the website to CMS or have the site content
>> in
>> >> the
>> >> >> >> current form in git and push the generated html using svnpubsub?
>> >> >> >
>> >> >> >
>> >> >> > I'm guessing that for an initial transition Jekyll + svnpubsub
>> would
>> >> >> > certainly be something worth trying out. Which SVN repo (folder)
>> >> should
>> >> >> we
>> >> >> > use for this? Do we need to request that an SVN repo be created
>> for
>> >> this
>> >> >> > purpose?
>> >> >> >
>> >> >> > ap
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Olivier Lamy
>> >> >> Ecetera: http://ecetera.com.au
>> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >> >>
>> >> >
>> >> >
>> >>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>
>
Re: Web site
Posted by Becca Wood <si...@gmail.com>.
I set the Jenkins job up but Adrian has karma on CloudBees so it is
currently running on his account. I can set it up to run on my account,
but it would be ideal to have an account for it to run on that we could all
have access to in order to work on jobs.
On Tue, May 7, 2013 at 11:49 PM, Olivier Lamy <ol...@apache.org> wrote:
> nope Jenkins ASF cannot commit to svn.
>
> Usually for other projects I'm involved @asf, I setup that in my
> private cloudbees instance so no problem for password.
> Let me know if you think it's a good idea.
>
> 2013/5/8 Ignasi <ig...@gmail.com>:
> > +1. If ASF CI can commit to the svn, that would be the fastest way to
> > migrate.
> > El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
> >
> >> I'm guessing it would actually be trivial to just port the cloudbees job
> >> Becca setup over to ASF jenkins and just add a step to do an svn commit
> of
> >> the resulting artifacts.
> >>
> >>
> >> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <mattstep@mattstep.net
> >> >wrote:
> >>
> >> > I'm guessing it would actually be trivial to just port the cloudbees
> job
> >> > Becca setup over to ASF jenkins and just add a step to do an svn
> commit
> >> of
> >> > the resulting artifacts.
> >> >
> >> >
> >> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org>
> wrote:
> >> >
> >> >> ETA: all is in place.
> >> >> See http://jclouds.incubator.apache.org :-)
> >> >> The svn path to populate is here:
> >> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
> >> >> Note there are some prerequisite with having incubator logo sample:
> >> >> http://helix.incubator.apache.org
> >> >> No time now to work on the infra to publish the real content (I will
> >> >> see later except if someone beat me)
> >> >>
> >> >>
> >> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
> >> >> >> https://www.apache.org/dev/project-site#intro and make a call on
> if
> >> >> you
> >> >> >> would like to port the website to CMS or have the site content in
> >> the
> >> >> >> current form in git and push the generated html using svnpubsub?
> >> >> >
> >> >> >
> >> >> > I'm guessing that for an initial transition Jekyll + svnpubsub
> would
> >> >> > certainly be something worth trying out. Which SVN repo (folder)
> >> should
> >> >> we
> >> >> > use for this? Do we need to request that an SVN repo be created for
> >> this
> >> >> > purpose?
> >> >> >
> >> >> > ap
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Olivier Lamy
> >> >> Ecetera: http://ecetera.com.au
> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >> >>
> >> >
> >> >
> >>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: Web site
Posted by Olivier Lamy <ol...@apache.org>.
nope Jenkins ASF cannot commit to svn.
Usually for other projects I'm involved @asf, I setup that in my
private cloudbees instance so no problem for password.
Let me know if you think it's a good idea.
2013/5/8 Ignasi <ig...@gmail.com>:
> +1. If ASF CI can commit to the svn, that would be the fastest way to
> migrate.
> El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
>
>> I'm guessing it would actually be trivial to just port the cloudbees job
>> Becca setup over to ASF jenkins and just add a step to do an svn commit of
>> the resulting artifacts.
>>
>>
>> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <mattstep@mattstep.net
>> >wrote:
>>
>> > I'm guessing it would actually be trivial to just port the cloudbees job
>> > Becca setup over to ASF jenkins and just add a step to do an svn commit
>> of
>> > the resulting artifacts.
>> >
>> >
>> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org> wrote:
>> >
>> >> ETA: all is in place.
>> >> See http://jclouds.incubator.apache.org :-)
>> >> The svn path to populate is here:
>> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
>> >> Note there are some prerequisite with having incubator logo sample:
>> >> http://helix.incubator.apache.org
>> >> No time now to work on the infra to publish the real content (I will
>> >> see later except if someone beat me)
>> >>
>> >>
>> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
>> >> >> https://www.apache.org/dev/project-site#intro and make a call on if
>> >> you
>> >> >> would like to port the website to CMS or have the site content in
>> the
>> >> >> current form in git and push the generated html using svnpubsub?
>> >> >
>> >> >
>> >> > I'm guessing that for an initial transition Jekyll + svnpubsub would
>> >> > certainly be something worth trying out. Which SVN repo (folder)
>> should
>> >> we
>> >> > use for this? Do we need to request that an SVN repo be created for
>> this
>> >> > purpose?
>> >> >
>> >> > ap
>> >>
>> >>
>> >>
>> >> --
>> >> Olivier Lamy
>> >> Ecetera: http://ecetera.com.au
>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>
>> >
>> >
>>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Ignasi <ig...@gmail.com>.
+1. If ASF CI can commit to the svn, that would be the fastest way to
migrate.
El 08/05/2013 08:35, "Matt Stephenson" <ma...@apache.org> escribió:
> I'm guessing it would actually be trivial to just port the cloudbees job
> Becca setup over to ASF jenkins and just add a step to do an svn commit of
> the resulting artifacts.
>
>
> On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <mattstep@mattstep.net
> >wrote:
>
> > I'm guessing it would actually be trivial to just port the cloudbees job
> > Becca setup over to ASF jenkins and just add a step to do an svn commit
> of
> > the resulting artifacts.
> >
> >
> > On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org> wrote:
> >
> >> ETA: all is in place.
> >> See http://jclouds.incubator.apache.org :-)
> >> The svn path to populate is here:
> >> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
> >> Note there are some prerequisite with having incubator logo sample:
> >> http://helix.incubator.apache.org
> >> No time now to work on the infra to publish the real content (I will
> >> see later except if someone beat me)
> >>
> >>
> >> 2013/5/8 Andrew Phillips <an...@apache.org>:
> >> >> https://www.apache.org/dev/project-site#intro and make a call on if
> >> you
> >> >> would like to port the website to CMS or have the site content in
> the
> >> >> current form in git and push the generated html using svnpubsub?
> >> >
> >> >
> >> > I'm guessing that for an initial transition Jekyll + svnpubsub would
> >> > certainly be something worth trying out. Which SVN repo (folder)
> should
> >> we
> >> > use for this? Do we need to request that an SVN repo be created for
> this
> >> > purpose?
> >> >
> >> > ap
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Ecetera: http://ecetera.com.au
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
> >
> >
>
Re: Web site
Posted by Matt Stephenson <ma...@apache.org>.
I'm guessing it would actually be trivial to just port the cloudbees job
Becca setup over to ASF jenkins and just add a step to do an svn commit of
the resulting artifacts.
On Tue, May 7, 2013 at 11:34 PM, Matt Stephenson <ma...@mattstep.net>wrote:
> I'm guessing it would actually be trivial to just port the cloudbees job
> Becca setup over to ASF jenkins and just add a step to do an svn commit of
> the resulting artifacts.
>
>
> On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org> wrote:
>
>> ETA: all is in place.
>> See http://jclouds.incubator.apache.org :-)
>> The svn path to populate is here:
>> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
>> Note there are some prerequisite with having incubator logo sample:
>> http://helix.incubator.apache.org
>> No time now to work on the infra to publish the real content (I will
>> see later except if someone beat me)
>>
>>
>> 2013/5/8 Andrew Phillips <an...@apache.org>:
>> >> https://www.apache.org/dev/project-site#intro and make a call on if
>> you
>> >> would like to port the website to CMS or have the site content in the
>> >> current form in git and push the generated html using svnpubsub?
>> >
>> >
>> > I'm guessing that for an initial transition Jekyll + svnpubsub would
>> > certainly be something worth trying out. Which SVN repo (folder) should
>> we
>> > use for this? Do we need to request that an SVN repo be created for this
>> > purpose?
>> >
>> > ap
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>
>
Re: Web site
Posted by Matt Stephenson <ma...@mattstep.net>.
I'm guessing it would actually be trivial to just port the cloudbees job
Becca setup over to ASF jenkins and just add a step to do an svn commit of
the resulting artifacts.
On Tue, May 7, 2013 at 8:50 PM, Olivier Lamy <ol...@apache.org> wrote:
> ETA: all is in place.
> See http://jclouds.incubator.apache.org :-)
> The svn path to populate is here:
> https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
> Note there are some prerequisite with having incubator logo sample:
> http://helix.incubator.apache.org
> No time now to work on the infra to publish the real content (I will
> see later except if someone beat me)
>
>
> 2013/5/8 Andrew Phillips <an...@apache.org>:
> >> https://www.apache.org/dev/project-site#intro and make a call on if
> you
> >> would like to port the website to CMS or have the site content in the
> >> current form in git and push the generated html using svnpubsub?
> >
> >
> > I'm guessing that for an initial transition Jekyll + svnpubsub would
> > certainly be something worth trying out. Which SVN repo (folder) should
> we
> > use for this? Do we need to request that an SVN repo be created for this
> > purpose?
> >
> > ap
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: Web site
Posted by Olivier Lamy <ol...@apache.org>.
ETA: all is in place.
See http://jclouds.incubator.apache.org :-)
The svn path to populate is here:
https://svn.apache.org/repos/asf/incubator/jclouds/site-content/
Note there are some prerequisite with having incubator logo sample:
http://helix.incubator.apache.org
No time now to work on the infra to publish the real content (I will
see later except if someone beat me)
2013/5/8 Andrew Phillips <an...@apache.org>:
>> https://www.apache.org/dev/project-site#intro and make a call on if you
>> would like to port the website to CMS or have the site content in the
>> current form in git and push the generated html using svnpubsub?
>
>
> I'm guessing that for an initial transition Jekyll + svnpubsub would
> certainly be something worth trying out. Which SVN repo (folder) should we
> use for this? Do we need to request that an SVN repo be created for this
> purpose?
>
> ap
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Web site
Posted by Andrew Phillips <an...@apache.org>.
> https://www.apache.org/dev/project-site#intro and make a call on if
> you would like to port the website to CMS or have the site content
> in the current form in git and push the generated html using
> svnpubsub?
I'm guessing that for an initial transition Jekyll + svnpubsub would
certainly be something worth trying out. Which SVN repo (folder)
should we use for this? Do we need to request that an SVN repo be
created for this purpose?
ap
Re: Web site
Posted by Suresh Marru <sm...@apache.org>.
Hi All,
Can you all please read the - https://www.apache.org/dev/project-site#intro and make a call on if you would like to port the website to CMS or have the site content in the current form in git and push the generated html using svnpubsub?
If you want to play a bit with CMS and then decide, I can help bootstrapping a bare bone site.
Suresh
On May 7, 2013, at 3:23 PM, Matt Stephenson <ma...@apache.org> wrote:
> 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 <ad...@gmail.com>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 <da...@gnsa.us> wrote:
>>
>>> On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <an...@apache.org>
>>> 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
>>>
>>
Re: Web site
Posted by Matt Stephenson <ma...@apache.org>.
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 <ad...@gmail.com>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 <da...@gnsa.us> wrote:
>
> > On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <an...@apache.org>
> > 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
> >
>
Re: Web site
Posted by Adrian Cole <ad...@gmail.com>.
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 <da...@gnsa.us> wrote:
> On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <an...@apache.org>
> 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
>
Re: Web site
Posted by David Nalley <da...@gnsa.us>.
On Tue, May 7, 2013 at 2:15 PM, Andrew Phillips <an...@apache.org> 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
Re: Web site
Posted by Andrew Phillips <an...@apache.org>.
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
Re: Web site
Posted by Becca Wood <si...@gmail.com>.
Hello,
I already addressed the issue of moving the jclouds.github.com repo over in
this jclouds github issue: https://github.com/jclouds/jclouds/issues/1576
My suggestion was: "Moving over jclouds.github.com will mean that we will
need to run Jekyll on everything. It could just be done on Jenkins or
CloudBees which would then just push the website over onto Apache's
servers. We'll also need to freeze the content for the DNS time out
interval so people don't see two different versions of our docs."
What do you think of my suggestion?
Thanks!
Becca
On Tue, May 7, 2013 at 5:59 AM, David Nalley <da...@gnsa.us> wrote:
> On Tue, May 7, 2013 at 6:31 AM, Olivier Lamy <ol...@apache.org> wrote:
> > Hi,
> > Where/how/etc.. is generated the content from http://www.jclouds.org ?
> > The goal is to have it at jclouds.incubator.apache.org.
> >
> > Let me know and I can work on that.
> >
>
> https://github.com/jclouds/jclouds.github.com
>
> (incidentally, this is a repo I did not migrate to git, despite it
> being in the proposal as being part of the donation.)
>
> --David
>
Re: Web site
Posted by David Nalley <da...@gnsa.us>.
On Tue, May 7, 2013 at 6:31 AM, Olivier Lamy <ol...@apache.org> wrote:
> Hi,
> Where/how/etc.. is generated the content from http://www.jclouds.org ?
> The goal is to have it at jclouds.incubator.apache.org.
>
> Let me know and I can work on that.
>
https://github.com/jclouds/jclouds.github.com
(incidentally, this is a repo I did not migrate to git, despite it
being in the proposal as being part of the donation.)
--David