What is the Upgrade procedure in regard of Sonarqube Server and Scanner.
We have an existing Sonarqube Server 9.9.1 LTS and the Sonar Scanner 4.8.0. using the cfamily build-wrapper.
Is it required to upgrade client and server environment at the same time ?
Is the old Sonar Scanner 4.8.0 and build wrapper compatible with the new Sonarqube Server 2025.1 LTS ?
Is the new Sonar Scanner 7.0.2 and build wrapper compatible with the old Sonarqube 9.9.1 LTS ?
You can download the matching build wrapper from your SonarQube instance like described in the docs
Using powershell i downloaded and extracted <Your SonarQube Server URL>/static/cpp/build-wrapper-win-x86.zip and then called the build.
If you download it on each build, you also don’t need to include it in the environment path.
We know how to obtain all artifacts.
It is about the procedure of a rolling update and the compatibility of different versions.
The client tools ( build-wrapper and scanner ) are used in many branches and the build definition is included.
Upgrading that in all branches together with the server at the same time is not really applicable without taken down the build and test automation/production for a longer time period , which would interrupt development for many developers.
For other commercial tools with client/server architecture it is possible to use for example a newer client with an older server or vice versa. That would allow for example to upgrade one branch first with new client tools, validate the functionality and port that step by step to other branches. The new server would be later setup from a backup and validated with an extra branch and when that works the server is swapped in a nightly maintenance window.