SonarQube upgrade from 2025.4 lta to 2026.1 lta sonarscaner and java 21

SonarQube Server / Community Build
,
1

Version of Sonarqube: 2025.4 LTA

Deployed: docker/bitbucket pipeline

Currently we are running sonarqube 2025.4 LTA and plan to upgrade to 2026.1 LTA

We have a large number of repos that use the sonar scanner 7 and java 17

Are we able to change all the sonar scanners to version 8.0.1 and change to java 21 prior to upgrading?

I have done some testing with sonar scanner 8.0.1 with java 21 and also the maven equivalent. It all seems to work fine but I’m not sure if there is any cavoites or issues that would arise if we did this.

Thank you,

Josh Becker

2

Hi Josh,

Current scanners pull the required Java version from the server. I don’t see a reason not to go ahead and upgrade the scanner.

 
HTH,
Ann

3

Thank you for this information.

I do have one more question about bandwidth and auto provisioning.

When using the docker image for the CLI with the 8.0.1 scanner.

I noticed that it had the java version of 21 (expected). When the auto provisioning is enabled, it downloads 17 (expected). If we were to disable the auto provisioning, would it still download java 17 or would it not.

Thank you,

Josh Becker

4

Hi Josh,

The download is auto-provisioning is the download. Disable auto-provisioning and the download goes away.

 
HTH,
Ann

5

@ganncamp If using the SonarScanner Docker Image, say the latest 8.0.1 version which comes packaged with Java 21, it doesn’t need to download it. In this case, would you agree it would make sense then to disable the auto-provisioning?

6

Hi @zusijepi,

Yes, it would make sense to me to disable auto-provisioning in this case.

 
HTH,
Ann