Moving from sonar.opendaylight.org to Sonarcloud.io
Eric Ball <eball@...>
We here at the LF Release Engineering team are working on a move from hosted SonarQube instances to the cloud-based Sonarcloud service. To that end, there is currently a proposed change to all Sonar jobs that would move them to Sonarcloud: https://git.opendaylight.org/gerrit/c/releng/builder/+/85644
Sonarcloud has more features and better language support than SonarQube, and it will remove the hosting and maintenance costs associated with the SonarQube server. Our plan is to decommission the SonarQube server about a month after we make the move to Sonarcloud.
You can view the OpenDaylight Sonarcloud page here: https://sonarcloud.io/organizations/opendaylight/projects
Currently, the only projects showing results are those that have run and passed on the sandbox. Once the change is merged, all projects will show results after their next successful run.
You may notice that while quantitative numbers like code coverage and duplication haven't changed, the number of bugs/vulnerabilities/code smells may have changed significantly (most likely an increase). This is due to Sonarcloud using much more up-to-date Quality Profiles than ODL's SonarQube instance, so this should be considered an improvement in results (even though I understand that it can be a pain to suddenly have a backlog of issues where there were few or none before). These profiles can be customized, so if anyone sees something coming up that absolutely should not be in the results, we can remove it from the Quality Profile.
Please let me know if you have any questions, or if you'd like to bring this up for discussion during the next TSC meeting.
Note: ovsdb is using a custom Sonar template. This will need to be changed to work with Sonarcloud, or (preferably) changed to use global-jjb templates. If there's something our global-jjb jobs do not currently support, we should be able to add that functionality.
The Linux Foundation