Sonar Community Roundup, November 2 - November 8

Hey all!

Thanks for another great week in our Community. The Community Managers at Sonar celebrated 3-years of Community Management at Sonar all together in the Austin office with cake!

We’re grateful 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 (formerly known as SonarQube):

SonarQube Cloud (formerly known as SonarCloud):

  • Folks who are using the very latest version of NodeJS (23) are facing issues with JRE auto-provisioning while using the Scanner for NPM. Shoutout to @Patrice_Scribe for letting us know! SCANNPM-55

SonarQube for IDE (formerly known as SonarLint):

  • For as long as I can remember, users have reported Symbol building is not allowed from CLion when using SonarQube for IntelliJ. We have written these errors off before as unrelated to SonarQube for IntelliJ itself, but it’s time we did something about them. SLI-1675 will try to address this. Thanks for the final push, @Marco_Arnaboldi and @Logan_Barnes!

  • After @Pigelvy bribed the developers last week with coffee flown in from exotic locations, we released the feature this week to allow IntelliJ users to choose their own JRE. :tada: He then pointed out that we haven’t updated the docs yet for that. Thanks for keeping us honest! It’s on the way. :sweat_smile:

Rule & Languages Improvements:

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 recognitions 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.

@ganncamp, @Colin, @steve.chen and @leith.darawsheh

3 Likes