I am attempting to set the leak period in SonarQube 5.6.5 using Sonar Scanner with a properties file or command line argument, but I am having no success.
I would like to set the sonar.timemachine.period1
property to a specific version, e.g., 1.0.0
, as is mentinoned in solution 2 (using sonar-project.properties
) or solution 3 (using command line paramter, e.g., -Dsonar.timemachine.period1=1.0.0
) of the accepted answer for Sonar runner, seeonly newly introduced issues.
Here is the scenario that reproduces my issue.
- Run analysis with
sonar.projectVersion=1.0.0
. - Run analysis with
sonar.projectVersion=2.0.0
andsonar.timemachine.period1=1.0.0
. - Run analysis with
sonar.projectVersion=3.0.0
andsonar.timemachine.period1=1.0.0
.
After the second and third analysis I would expect the leak period to be "since 1.0.0
" (which is the behavior if I manually set the leak period in the SonarQube admin section to 1.0.0
). Instead, for the third analysis the leak period is being set to 2.0.0
.
What am I missing? Is this a bug?