+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" <[email protected]> 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 <[email protected] > >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 <[email protected]> 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 <[email protected]>: > >> >> 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 > >> > > > > >
