SonarQube uses now a different versions scheme since 10.8 (is now 24.12.0.100206-community)

[jonesbusy]

Name and Version

bitnami/sonarqube

What is the problem this feature will solve?

Hi,

Since what is supposily be 10.8, Sonar changed their version scheme for the community build.

Instead of 10.8 it's now 24.12.0.100206-community

We change the version detection to use this new calendar like versioning ?

See

• https://github.com/SonarSource/docker-sonarqube/blob/f4f646eed2d589359ff6e806fb648049ac6ee67c/community-build/Dockerfile#L17C23-L17C37
• https://hub.docker.com/_/sonarqube
• https://community.sonarsource.com/t/sonarqube-community-build-24-12-0-100206-released/131515
• https://community.sonarsource.com/t/updates-to-sonar-s-community-functionality/130732

What is the feature you are proposing to solve the problem?

Changing the version scheme and ensure future update of SonarQube community build gets build

What alternatives have you considered?

No response

[carrodher]

Hi, thanks for letting us know. Yes, our automation already detected the new version, although since it's a major version it requires manual changes on our side. We'll update this thread once released this new major.

[carrodher]

The new container image has already been released (see above PR), you can consume it as usual at https://hub.docker.com/r/bitnami/sonarqube/tags. Now, we're working on bundling this version in the Helm chart.