Migration guide to app version 5

This page helps customers upgrading from app versions 4.x to the 5.x version line. When upgrading from an older app version 2.x, check https://mibexsoftware.atlassian.net/wiki/spaces/MSS/pages/2546565121 first.

Removal of compatibility mode can require configuration of “Sonar analysis directory” option

If you were using the app’s compatibility mode in older versions of the app, you might not see any annotations in your pull requests after the upgrade to app version 5.

This can happen e.g. if you trigger the SonarQube analysis from a different directory than the repository root, or when using a different Sonar analysis directory with sonar.projectBaseDir. In this case, you must configure the relative path to the analysis directory in the field “Sonar analysis directory” in your repository settings → Sonar:

Open

To give you an example, let’s say you invoke the Sonar analysis from within a subdirectory of your repository:

$ cd multimod/src

$ mvn sonar:sonar

In this case, you would have to fill in the value multimod/src in the field Sonar analysis directory and refresh the Sonar analysis. Afterwards, you should see the annotations in your pull request again:

Open

Move of SonarQube edition setting from repo to SonarQube server level including auto-detection can require adjustment

In older app versions, the option to use the commercial branching/pull request support was part of the repository settings.

With app version 5, the SonarQube edition type is now auto-detected, and can only be changed in the SonarQube server settings, but not in the repository anymore:

In case the SonarQube edition is wrongly detected, or if you want to override it due to some reasons, you can do this after the upgrade under Bitbucket admin → Sonar → edit SonarQube server configuration.

Troubleshooting

If you experience any problems during the app upgrade, check our Troubleshooting guide, and in case of permanent issues, let us know by creating a support ticket.