Q - Will the talk only cover Sonar Tools/Features or will there be a more general discussion of clean code as well?
A - Today’s talk will be around Clean Code and C++. Please check the link of our previous webinar that was more of a general discussion of clean code : https://youtu.be/dY76ed3YBaw
Q - Can we configure SonarLint to include certain rulesets - eg: cppcoreguidelines, AUTOSAR C++14 standards, MISRA standards etc.?
A - SonarLint already covers cppcoreguidelines and a significant part of the C++ MISRA standard. We don’t plan to support AUTOSAR, but we are working on supporting the next Misra standard 202x
Q - As far as you know, is there any static analysis tool that has also references to the “C++ Core Guidelines”?
A - SonarLint,SonarCloud, and SonarQube cover C++ Core Guidelines.
Q - Do you plan adding an automated “fixer” in certain criterias off analyzed Sonar results?
A - We already do that in SonarLint, we call them quick fixes. You can check:
Q - Can we use Jenkins plan and Bitbucket?
A - Yes it is supported!
Q - Is there a VisualStudio integration?
A - Yes, SonarLint is available in the Visual Studio for free. You can install it from the VS marketplace.
Q - Is it mandatory to connect SonarLint to SonarCloud/Qube?
A - No, it is not, but if you do you will be able to extend SonarLint capabilities by syncing the Quality profile, excluded files, and the suppressed issues
Q - Is this tools support popular libs? QT for example
A - Yes, we can analyze code using QT! Our solution is libraries and build-system independent
Q - Is it possible to write clean code in a agile paradigm?
A - Yes, by following the Clean as You Code approach encouraged by our tools:
Q - Is it possible to define my own C++ rules without using SonarQube? I mean I am using just SonarLint.
A - If you mean enabling and disabling rules, then the answer is yes.
You can do that in SonarLint. If you mean implementing custom rules, the answer is no.
We are happy to implement the rules suggested by our users. If you have rule ideas, please post them on the Community.
State of Software Code Report
CISQ “The Cost of Poor Software Quality in US: A 2022 Report”