On Fri, Aug 23, 2013 at 4:09 PM, Maureen Barger <mobar...@gmail.com> wrote:
> I am currently planning an upgrade from SVN 1.5 (using svnserve and > ssh tunnel) to SVN 1.8.1 fronted with Apache and webdav using AD for > authNz. > We have about 50 repos. I'll be moving from an older Ubuntu 8 install > to Centos 6 x64. > > My thought was I could upgrade the SVN installation in place, bringing > the repo up to 1.8 and then dump those repos and bring them online in > the new environment. > If it were me, I would not upgrade the repositories. SVN 1.8 can just serve the old repositories. I would do the upgrade and only after I was using it for a while would I then consider to start doing a dump/load on the repositories. You could then do them one by one as desired. The main benefit in upgrading the repository is to use less disk space. > We currently use Eclipse as our IDE and Jenkins as our CI tool with > Nexus as the object repo. I was thinking to leave the upgrade of > Eclipse client and svnkit to the indiviidual so they can decide what > direction to take with their working copies et al. Yes, your clients can already be using 1.8 if they want to. There is no need to upgrade the client either before or after the server. Let the clients manage it. Only exception is if there are specific new features you want to implement across the board. If you do a lot of branching and merging, it would be a good idea for the people that do merge to all be using the same version. Likewise, there are other features that might be like this. > I do not foresee > any changes I would need to make to Jenkins or Nexus. > Just the URL to access the repository will change. > > Has anyone made a jump this large before? Any comments about my upgrade > plan? > There is nothing unusual about this. People have jumped from 1.1 to 1.8. -- Thanks Mark Phippard http://markphip.blogspot.com/
