{"id":715,"date":"2013-11-03T16:12:49","date_gmt":"2013-11-03T15:12:49","guid":{"rendered":"http:\/\/qualilogy.com\/en\/?p=715"},"modified":"2013-11-03T17:19:52","modified_gmt":"2013-11-03T16:19:52","slug":"sonarqube-upgrade-prerequisites","status":"publish","type":"post","link":"http:\/\/qualilogy.com\/en\/sonarqube-upgrade-prerequisites\/","title":{"rendered":"SonarQube upgrade – Prerequisites"},"content":{"rendered":"

\"SonarUpgradeImg\"<\/a><\/p>\n

We have seen previously how to migrate SonarQube from Tomcat to a Windows service<\/a> and how to use SonarQube as a Windows service with Jenkins under Tomcat<\/a>,<\/p>\n

I did use<\/span> the same<\/span> release 3.5.1<\/span> to perform this<\/span> migration from<\/span> Tomcat<\/span> to a<\/span> Windows service<\/span>, and as<\/span> it is<\/span> already<\/span> old<\/span>, this will be<\/span> an opportunity to make<\/span> an upgrade<\/span> of Sonarqube and<\/span> update our<\/span> environment<\/span> with<\/span> new versions of\u00a0<\/span>plugins.<\/span>
\n<\/span><\/p>\n

I will document this operation in<\/span> two articles<\/span>, including<\/span> this first<\/span> one to present<\/span> the steps<\/span> to prepare our<\/span> upgrade.<\/span> This will also be<\/span> the opportunity to see<\/span> how to do an Oracle<\/span> backup<\/span>.<\/span><\/span><\/p>\n

Task list<\/h1>\n

At first, I will start planning the different actions to perform. <\/span>Not that this operation is complicated , but it is an opportunity to make an inventory of our environment, and especially the plugins evolutions. <\/span>An upgrade is not just an installation of a new version of SonarQube but also an update of our plugins. <\/span>And I like to know what changes are available, if there are new rules to test, a new feature to implement, etc.
\n<\/span><\/span><\/p>\n

Also, to list the plugins to upgrade allows us to keep some trace of the evolutions of your environment, and I suggest you do the same, especially if you use SonarQube in a professional way, in your company. <\/span>A new rule or the modification of an existing rule in your code analysis can trigger a surge of defects in the SonarQube dashboard, and your developers might not understand the cause of this sudden deterioration in the quality of their application.<\/span><\/span><\/p>\n

Their first reaction could be to question the validity of your analysis, and in this case, you better be ready to explain which new version of a plugin has introduced which new rule at the origin of these new defects. Always good to k<\/span>eep a document to trace the changes in your environment.<\/span><\/span><\/p>\n

Update Center<\/h2>\n

I keep all the mails from the SonarQube mailing list, that announce new release of the software or of a plugin, mais there is a simpler way to know which of the plugins you have installed are up-to-date or not: the Update Center.<\/p>\n

\"SonarQube<\/a>First, we will connect into SonarQube as an Admin, from the SonarQube dashboard.<\/p>\n

Then, we go in the Update Center page from the menu:<\/p>\n

\"SonarQubeLogin2\"<\/a><\/p>\n

‘Settings’ and then the sub-menu ‘Configuration’.<\/p>\n

From this configuration page, we choose the menu ‘Update Center’ in order to display the corresponding screen, with different tabs that show us:<\/p>\n