On learning about integrating Sonarqube to CI/CD pipeline, I came across the Sonarqube Jenkins plugin which most of the online blogs recommends.
After configuring it, I realized that the working is the same as that of running the sonar-scanner through the command line using below command.
sonar-scanner.bat -D"sonar.projectKey=test" -D"sonar.sources=." -D"sonar.host.url=http://localhost:9000" -D"sonar.login=erwerwerwerwer"
Same is applicable for any tool, as most can be executed through command line.
So I am confused about,
what's the advantage of using a plugin over just running the tools as windows batch command in Jenkins build step.?