SonarQube 10.6 Enterprise Edition

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube, Scanner.
  • how is SonarQube deployed: zip, Docker, Helm
    Docker
  • what are you trying to achieve
    I want to know if after Enterprise version 10.6, there is no longer a need to use build wrapper to collect compilation processes for C/C++projects.
  • what have you tried so far to achieve this
    Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

It remains an option, and probably gives the most accurate analysis. Details on various analysis modes (including the new AutoConfig mode, without build wrapper or build) is available here.

okay, thank you; I have another question. I didn’t understand how to use Autoconfig. The documentation states that Autoconfig is enabled by default. Do I need to configure it when running SonarScanner, or do I not need to modify it as before? Just cancel the JSON file address generated by build wrapper.I would like to know if there is a specific tutorial available.

It’s really just a matter of removing the build-wrapper and removing (or even just commenting out!) sonar.cfamily.compile-commands

It can be further customized, but as a start, you can just pretend you’re scanning any other kind of code (Javascript, HTML…) that uses the vanilla sonar-scanner.