![]() ![]() With everyone in the loop, issues can be addressed promptly, improving the overall software quality and delivery. See the following links for instructions on setting up Connected Mode for each supported IDE:Ĭonnected Mode allows SonarQube to send smart alerts to individuals or teams when new issues are discovered. You'll get all of the context in your IDE that you need to triage and fix security problems thereby making sure the code you commit is safe. In Connected Mode, you'll see the taint analysis issues SonarQube raised in your project. When using SonarLint alone, taint analysis issues found by commercial editions of SonarQube aren't raised in SonarLint for performance reasons (we don't want to slow down your editing). With Connected Mode, the same customized rule set is applied in both your IDE and in SonarQube, and you're notified in your IDE when your local instance isn't meeting the project's quality gate standards. ![]() If you're using a different quality profile in SonarQube, new issues might be raised in SonarQube even though your commit looked clean in SonarLint. When using SonarLint, the Sonar way Quality Profile is used by default and users can customize their ruleset. Shared code quality and security expectations SonarLint's Connected Mode connects SonarLint to your SonarQube project and provides additional benefits you won't get by using SonarLint or SonarQube alone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |