Looking at the recommendation to follow all the requirements through the various version to upgrade from 2.10.0 to 3.5.0 seems like there would be a huge opertunity for something to go wrong.
My question: Is there a scripted process for performing such an upgrade?
I'm extreemly nervous about performing so many steps and taking down the entire platform for much longer than necessary. Recovering inbetween these individual upgrades, especially if there are db modifications, would make this upgrade way more fun than necessary.
You should certainly take backups of your database and your FISHEYE_INST directory before upgrading.
I would suggest making a copy of your instance and testing the upgrade process on that, as you are upgrading from a fairly old version, but the upgrade is no more complex from an administrative point of view than any other upgrade.
A test upgrade would tell you how long your instance will take to upgrade, which is difficult to predict as it depends on the size, type and layout of your repositories.
Yah, all good suggestions and I do have an environment for such things. Maybe I should have posted my question a little differently...
Can I use the 3.5.x upgrade on my 2.10.0 versions directly or would I have to run through each version sequentially? I'm hoping the former is the suggested route. :)
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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