So I just stumbled upon this huge upcoming change that is set to arrive in SonarQube 8.0:
https://jira.sonarsource.com/browse/MMF-1579
…and it makes me very nervous. After reading the description and skimming some of the linked issues, it’s become apparent that the existing leak period setting will be replaced by something more restrictive, removing the ability for users to set the new code baseline to a specific version or date and instead requiring us to set it to a specific analysis ID.
If I understand correctly, this will make many of my teams’ main use cases of the “New Code Period” impossible to satisfy (even if this new setting were configurable as a scan parameter) since we most often want to target a “version” without needing to be aware of the analysis ID that corresponds to the last scan of that version.
Does the SonarQube team consider ours as invalid/irrelevant use cases? Are there cleaner alternatives? Am I just misunderstanding the issue description? I’m not sure, but perhaps this is a conversation for a new topic. (Update: Topic posted here.)
In any case, to hopefully get back on-topic, I still stand by my original request of making the “new code period baseline” (or whatever it will be called) an analysis parameter.