|Table of Contents|
Upgrading From 1.X to 2.0
After the upgrade, you will have to reconfigure the SonarQube Runners.
Upgrading From 1.x to 1.7.1
The configuration of the plugin triggers has been totally rewritten for version 1.7.
If you were using triggers, this configuration will not be kept. You'll need to reconfigure the global configuration of the plugin as the configuration of your job.
So before upgrading, you'll have to keep the information on how you have configured the SonarQube Jenkins plugin and all your jobs.
However, the configuration will be simpler as you will only need to configure when you want to skip SonarQube analysis.
The SonarQubelight was removed, so any configuration of SonarQubelight will be lost.
After Installing SonarQube Jenkins Plugin 1.7.1
After the installation, you will need to reconfigure the global configuration.
And if the global configuration should be overloaded on a specific project, you will need to change the specific project configuration.
Warning message on "Configure Jenkins"
Some previous variables are no more used in SonarQube Jenkins plugin, you will probably see this:
Please check if the "data stored in old format" are SonarQube plugin data :
All errors "No such field hudson.plugins.sonar.SonarPublisher.configVersion" can be dismissed.
Troubles During the Upgrade
We have noticed that the upgrade may lead to have both version.
You may notice this on the error.log of Jenkins:
In this case, you can fix it by:
1. Stopping Jenkins,
2. Deleting sonar-1.6.1.hpi and sonar-1.6.1 located in ~/.jenkins/plugins,
3. Starting Jenkins