Skip to end of metadata
Go to start of metadata

By SonarSource and Waleri Enns – GNU LGPL 3 – Issue TrackerSources – Supported by SonarSource
More versions
SonarPython 1.10 – Apr 30, 2018 – SonarQube 6.7+ (Compatible with LTS)
Update Pylint rule definitions (Pylint 1.8.4).
DownloadRelease notes

Description

Enables the powerful SonarPython analyzer. Supports both Python 2 and Python 3.

First Analysis of a Python Project

  1. Install SonarQube Server (see Setup and Upgrade for more details)
  2. Install SonarQube Scanner and be sure your can call sonar-scanner from the directory where you have your source code
  3. Install SonarPython (see Installing a Plugin for more details)
  4. (Optional) Install Pylint if you want to activate Pylint rules
  5. Run your analysis with the SonarQube Scanner by executing the following command from the root directory of the project:

    sonar-scanner -Dsonar.projectKey=xxx -Dsonar.sources=.
  6. Follow the link provided at the end of the analysis to browse your project's quality in SonarQube UI

Further Analyses

Assuming steps 1-3 above have already been completed, you'll want to encapsulate your analysis parameters in a sonar-project.properties file at the root of your project (see a sample project on GitHub: https://github.com/SonarSource/sonar-scanning-examples/tree/master/sonarqube-scanner). Then subsequent analyses can simply be run with:

sonar-scanner

 

Advanced Usage

With SonarPython, you can:

 

 

  • No labels