Must-share information (formatted with Markdown):
-
which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)
sonarqube-server/10.7/
using it for a Kotlin/Java Android App through gradle commandsonar
-
how is SonarQube deployed: zip, Docker, Helm
I don’t know; IT set it up -
what are you trying to achieve
UsingNew Code
to scope Quality Gates to the latest version.
For this to work, we are sending the property “sonar.projectVersion”, “${newCodeVersion}” to sonarqube. We can confirm the version is being sent as it appears in the activity tab.
The problem we are running into is that the first occurrence of a version is not marking new code properly; instead, the version is moved by every analysis to the newest analysis instead of staying in place as a marker. -
what have you tried so far to achieve this
I also tried manually adding the version event on Jan 10th, but after some time it disappeared there and was seemingly overwritten with the newest entry again.
Version 32.03 was first sent to sonar (and appeared properly) on January 10th. But with each sync, it got pushed to the newest entry, so we don’t get to use the feature properly.
It got moved after the latest sync/analysis: