Sonar Community Roundup, December 28 - January 10

Hi all,

This week we welcome @carmen.m / Carmen Musat, who joins us as our new Community Program Manager. She’ll be focusing on community advocacy programs where she will help us reward and recognize our most active and enthusiastic community members.

If you’ve been around for a while, you may remember that in previous years we’ve disappeared for a while in early/mid-January for the annual company off-site. Well, that’s next week, so we’d appreciate it if you could be patient when we don’t respond immediately, and - if you have a few minutes to spare - look after each other for a little bit. We’ll be back soon to catch up on what we missed. :kissing_heart:

And in the meantime, we’re grateful for the feedback we’ve gotten this week, and for every time you give us feedback. So like every week we want to spend some time acknowledging everyone who prompted interesting discussions and gave us feedback to help us continuously improve.

SonarQube Server & SonarQube Community Build:

  • @Scott reported a bad in-app link to the SAML docs in Community Build. The link was (theoretically) correct, but the page was missing. It’s already been fixed!

  • @andi recommended updating the docs to be clear that the SARIF import supports “stacks”. Great idea! We’ll get it done.

  • A very long time ago (in 6.2 IIRC) we deprecated file-level complexity metrics. In SonarQube Community Build 25.1 we finally removed them. @guwirth pointed out that it’s probably worth documenting. We’ve updated the docs already and will take a look at the package information.

  • More significantly, back in October @guwirth flagged a performance degradation in analysis with SonarQube Server 10.x versus 9.9. His granular testing was significant in helping us isolate and address the problem(s). SONAR-22998, SONAR-24006, SONAR-23974, SONAR-24057

  • It seems refreshing an application - for example by reanalyzing one of its projects - no longer triggers the refresh of portfolios that include the application. Thanks @james_mck! It’s fixed in SONAR-24122

  • @Ricetrac helped us realize that AI Code Fix doesn’t use the proxy settings you’ve configured for SonarQube Server. Doh! SONAR-24165.

SonarQube for IDE:

  • macOS users of SonarQube for IntelliJ are noticing a Java icon in their doc when using SonarLint. That’s not something we expect. Thanks @Kyle! SLCORE-1105

SonarQube Cloud:

Rule & Languages improvements:

Scanners:

  • @Lostfields was struggling with a .NET analysis failure for a double-indexed file. While the latest versions of SonarScanner for .NET ignore user-set sources and test configurations, automatic analysis hasn’t caught up to that yet. In the meantime, we’ll update the documentation for this. Thanks!

  • @AidarGatin is experiencing a timeout during his Python analysis, and even debug logs aren’t helpful figuring out why. As a first step, we’ll improve the logging. SCANENGINE-58

Once more, we extend our thanks to everyone mentioned here - and those we may have missed - for their efforts in strengthening this community and enhancing our Sonar products.

Please leave your own shout-outs below – whether for another community member or a SonarSourcer who assisted you this week. If there’s someone you think should be acknowledged in next week’s roundup, don’t hesitate to let us know.

 
Ann

1 Like