Jira 7.0 to 7.13 upgrade

[Vyvyan Fuge]

Hi Again Guys.

As per your advice have conducted considerable testing of the upgrade process of JIra Core 7.0 to 7.13, within an isolated test environment. A am now looking for your assistance again with the upgraded instance of Jira failing to start a whole bunch of plugins.

Have 2 VMs running Server 2012 R2 with 24Gb RAM, 8 x 8 core CPUs and 100GB system partition. One VM ruinning Jira and the other running SQL 2012.

 After a few "gotchas" the following is the process taken to get to my present point.

1) Used SQL native tools to peform database backup

2) Stop Atlassian Jira service. Problems were experienced during initial attempt with failing to upgrade files that were locked by process.

3) Applied Full Control NTFS permissions to account running Jira upgrade to everything under c:\program files\Altlassian\*.*. Although the account is a Domain Admin account was unable to save the dbconfig.xml during the config.bat process.

Can detail the plugins not strating if you wish but there is so many of them and I can Cut\Paste the screen prompt.

HELP!!!

[Thomas Deiler]

Dear @Vyvyan Fuge,

a good page for your needs is this one. Anyway to go above 7.1.x you first have to upgrade to the latest 7.0.x.

But you already got loads of good information from Nic in your December question.

So long

Thomas

[Vyvyan Fuge]

Thanks Thomas for the quick response again.

Not sure if I'm missing something with your reply. In my December post I had confirmation that I could upgrade directly from 7.0.x to 7.1.3. This upgrade has been done as above. My issue is with a bunch of plugins failing to start.

Are you saying that that upgrade process needed a more stepped approach to avoid the plug-in issues I am experiencing?

[Thomas Deiler]

Dear @Vyvyan Fuge,

ups - missed this. Sorry,

My advice is to pull exactly the right versions of plugins that will fit to the Jira version. Place them inside the plugins directory and start Jira. Be sure that old plugins from a previous Jira version are removed.

When Jira starts up with errors, remove the plugin under suspect and add it later via UPM. Starting Jira with no plugins will normally not harm your data.

In rare cases the plugin versions may not be skipped due to migration actions they will perform. Best to read the release notes or contact the plugin vendor.

This is just a recommendation. Since the combinations of available and installed plugins is nearly infinite for each installation, this is just the best approach. 

So long

Thomas