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