Each time I have upgraded either Fisheye, Fisheye is no longer able to index those repositories until I re-upload the private key I had generated for it.
I followed the upgrade instructions and copied over the /var /cache and config.xml to the new instance. What can I do to not have to re-upload the private key for each repository I have Fisheye watching?
Thanks for pointing out this issue, we'll update the upgrade guide to include instructions on how to copy the SSH keys to the new version.
Another option is to split your installation into a FISHEYE_INST and a FISHEYE_HOME directory. That way, upgrading to a new version is as simple as backing up your FISHEYE_INST directory, unzipping the new version and starting FishEye from the new location.
More information on using a separate FISHEYE_INST directory can be found here.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs