Do I need sonar and sonar runner for Jenkins?

I want to set up Sonar with Jenkins. But I’m not sure if the Sonar site describes two different ways to do this or if there are two necessary steps:

As far as I understood it, it’s two different ways. If this is the case, what is the difference and what are the advantages and disadvantages (between the Sonar itself and Sonar runner)?

  • What is the password for jenkins user under MACOSX?
  • How to get the number of tests run in Jenkins with JUnit XML format in the post job script?
  • Store the console output of a build step execution in Jenkins pipeline
  • How can I know how long a Jenkins job has been in the wait queue after the job is finished?
  • Jenkins push-to-deploy setup for app-engine fails
  • Process only changed files
  • Jenkins Git Plugin does not receive posted Parameters
  • jenkins/hudson can't connect to github repo
  • Jenkins Lint Plugin not picking up results
  • How to get Jenkins to --fail-fast on Maven 2 builds?
  • Parsing an XML file within a Jenkins pipeline
  • Hudson vs Jenkins in 2012
  • One Solution collect form web for “Do I need sonar and sonar runner for Jenkins?”

    If you want to analyse a project with SonarQube and Jenkins, here’s what you need:

    • A SonarQube server up and running

    • A Jenkins server up and running with the SonarQube Scanner for Jenkins installed and configure to point to your SonarQube server

    • A job configured to run a SonarQube analysis on your project:

      • Using the default and standard SonarQube Scanner (suitable for most projects)

      • Using the SonarQube Scanner for MSBuild (for .NET solutions)

      • Using a post build action for Maven-based projects

    Everything is described more in details on the SonarQube Scanner for Jenkins documentation page.

    Git Baby is a git and github fan, let's start git clone.