- SonarQube Community Build
- Docker
- Scan local repo (in VSCode)
- Create new project in SonarQube, Connect from VS Code to that project
This is driving me nuts lol.
I just want to scan a local project with sonarqube. I do not want GitHub, and whatever else online/cloud eyes on this.
I use a self-hosted SonarQube Community server (updated today)
I already have an existing connection from my VSCode to it because I do analyze other projects (which are on github) with it too.
So I went into my sonarqube instance, added a project (call it My Project) and then in VS Code I opened my local project, I went to SonarQube setup section, I chose my existing connection, I added a project and selected the one I just created in SonbarQube
At the bottom of visual code it says “scanning 11 files” so I thought wow, fast and cool.
yet, zero issues found, so, no, this can’t be: I am not writing pixel perfect code.
Going back to SonarQube I see I am supposed to install some pip install pysonar and then run a terminal command
```
pysonar \
--sonar-host-url=https://my-host.com \
--sonar-token=my_token \
--sonar-project-key=My Project
```
??? I am confused.
Why can I not analyze from the comfort of the VS UI as I do with all other projects (which have a Github instance)?
Why does it say “scanning 11 files” but clearly doesn’t?
How do I actually use SonarQube locally without going an installing new packages for each new project (which might have different languages), and avoid use terminal, since I have the VisuaCode extension of SonarQube?