We are running Fisheye 3.3 with file:// access to our subversion repositories. We plan on upgrading our svn repositories to svn 1.8. We see that Fisheye 3.3 now supports 1.8, the question is after upgrading is there anything that we need to do on the fisheye side. Do we need to re-index, re-start the server (we actually plan on having fisheye down at the time of the svn upgrade), nothing?
There is nothing you need to do on the FishEye side to have it working seamlessly with the upgraded repository. In theory you don't even need to take FishEye down as svnadmin upgrade command should lock access to repository while upgrade is taking place, but it would be safer to take FishEye down for this operation.
Note http://svnbook.red-bean.com/en/1.6/svn.ref.svnadmin.c.upgrade.htmlexplains svnadmin upgrade performs only the minimum amount of work needed and if you want the most optmized repository state you may want to dump and subsequently load the dump into new repository. In this case you should definitelly take FishEye down while playing with the repositories.
Hope that helps,
We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events