SonarQube 9.9 LTS was released in February and we hope you’ve already seen our announcement and are working on your upgrade!
A new SonarQube LTS represents a huge amount of work. Since the release of the previous SonarQube LTS (8.9, in May 2021), there have been thousands of development tickets merged in SonarQube and its underlying components. This includes new functionality, improvements to existing features, and bug fixes.
It’s a lot, and if we tried to talk about every change, we’d be here a while. Since not everything can land in our big release announcements, I want to tell you about 9 cool features you might not know are included in the SonarQube 9.9 LTS.
SonarQube 9.9 LTS starts up 35% faster than SonarQube 8.9 LTS!
This was accomplished by reducing the number of checks made on the database when no plugins have changed between start-ups (and even still a 15% improvement when plugins have changed).
This means less downtime and faster troubleshooting – which is all anyone working in Operations could ask for.
SonarQube now detects when files have been moved as part of a pull request. This may sound minor, but it’s a big deal!
Previously, when files were renamed as part of a pull request, SonarQube identified those files as new and re-raised all the old issues in that moved code as being new in the PR. In SonarQube 9.9 LTS, the behavior is more in line with the user experience for analyzing branches, i.e. old issues in moved files are ignored, and developers can focus on what’s important: changed code.
Renamed files and changed some code? Don’t worry, SonarQube still detects those changed lines as being new code.
DevOps Platform Secrets (like Personal Access Tokens) could previously only be stored in SonarQube’s database in plain text. In SonarQube 9.9 LTS those secrets can be encrypted like any other setting, keeping them safe in the event of a security incident.
It has always been possible to “deactivate” a user in SonarQube, but this did not remove user information from the UI and from the database.
To comply with the strict GDPR requirement of some organizations, while maintaining the integrity of the information stored in SonarQube, we’ve introduced a new web service in SonarQube 9.9 LTS to allow for the anonymization of user data.
Programming languages are constantly evolving and new versions are regularly being released. SonarQube 9.9 LTS adds support for the latest versions of the programming languages you’re using, making sure analysis doesn’t fail on new language features and that rules stay relevant even in a new context.
|Language||SonarQube v8.9 (former LTS)||SonarQube v9.9 LTS|
|C++||C++20 (partial)||C++20 (except modules)|
* Rome wasn’t built in a day. :) SonarQube no longer fails to analyze C# 11 projects, but full support is still to come
Removing inactive projects from a SonarQube instance is good practice for SonarQube administrators, especially as instances grow larger and larger. It has always been possible for an administrator to bulk delete projects based on the last analysis, but only the date of the last analysis of the main branch was considered.
This could result in active projects being deleted by mistake.
In SonarQube 9.9 LTS when projects are deleted from an instance in bulk based on their analysis date – all branches and pull requests are considered!
Big companies don't often have a single set of administrators that can decide and administrate Quality Gates for all projects. And, in SonarQube 8.9 LTS, every user with Quality Gate administration rights can update and assign any Quality Gate so administrators wisely don't want to widely grant this right.
In SonarQube 9.9 LTS it’s possible to delegate the administration of customized Quality Gates to SonarQube users and groups to remove administrative overhead and give more autonomy to teams!
Never miss a new version of SonarQube with in-app notifications of new versions for system administrators.
SonarQube 9.9 is an LTS version – meaning it will be maintained for at least 18 months with security and bug fixes. It’s important to run the latest patch version for the best security and reliability.
In the Enterprise Edition of SonarQube, administrators gain the ability to increase the number of Compute Engine workers that process analysis reports. The Data Center Edition takes this further and allows operators to set up multiple SonarQube nodes to process even more.
And, there has always been a limitation that only one analysis per project could be analyzed at the same time. This was especially frustrating when pull requests (which are processed quickly) were held up by analyses of an unrelated branch.
With SonarQube 9.9 LTS, multiple pull request analyses for the same project can now be processed simultaneously, and while other branches are being analyzed. This means developers get the information they need faster than before, and their code changes will get merged sooner too.
This feature is opt-in and you can find more information in the documentation
If you haven’t tried SonarQube 9.9 LTS yet, I hope you now have 9 more reasons to prepare that upgrade with your team. This is a free version upgrade for all, and you can get the LTS in just a few clicks @ SonarQube Downloads.
Need more help getting started? Check the following resources:
- SonarQube LTS Upgrade Checklist
- Get help upgrading using the 9.9 LTS Upgrade category of the Sonar Community
In a few weeks, we'll share another 9 reasons to upgrade to SonarQube 9.9 LTS (or better yet, let you know how to take advantage of the instance you've already upgraded)!