SonarQube analysis is typically built directly into our CI/CD processes and provides feedback to the teams as the build is happening. SonarQube is an open-source tool that can scan and identify problems with code quality across several different technology stacks. 8.4.At Advanced we use SonarQube as our static code analysis tool. Across all programming languages and across all IDEs, you can expect recurring additions of new static analysis rules and even new languages based on interest and relevance! Make sure to get the big picture.

The SonarSource Language Team is continuously advancing its in-house bug and vulnerability detection engine. For example, just think of SonarLint detecting the branch you’re working on, and aligning its code analysis with what is reported in SonarQube/SonarCloud (now supporting branch and PR analysis). As more features make it to SonarQube/SonarCloud, we want to make sure they are also integrated with SonarLint whenever it provides value. SonarLint Connected Mode unlocks integrations with SonarQube/ SonarCloud, so that the issues reported in your IDE are in line with the project health and Quality Gate that your team is tracking. As such, SonarLint for VSCode may not offer all the features and capabilities it provides in other IDEs, however the end goal is feature parity with the other SonarLint members! We really want all developers, irrespective of the language and IDE they code in, to benefit from the full feature-set of SonarLint.Įnd-to-end experience for SonarQube and SonarCloud users VSCode is the youngest member of the SonarLint-supported family.

This should be available to all developers across all IDEs supported by SonarLint. Muting specific issues that you deem as not-applicableĮnabling non-default rules that you would like to be checked as you code Excluding specific files from SonarLint analysisĭeactivating specific rules that are not valuable to you

Sonarlint latest version