SonarQube Gradle Integration: Setup and Config

Integrating SonarQube into a Gradle project is straightforward once you know where the configuration lives. Unlike Maven, where the plugin runs as part of the build lifecycle automatically, Gradle uses an explicit sonar task that you trigger on demand. A single ./gradlew sonar command analyzes your Java or Kotlin code, collects test coverage data, and uploads everything to your SonarQube server. This guide covers the complete sonarqube gradle setup - from adding the plugin to build.gradle or build.gradle.kts through sonar properties configuration, multi-module project handling, JaCoCo code coverage integration, quality gate enforcement, and CI/CD pipeline examples for GitHub Actions and Jenkins. Both Groovy DSL and Kotlin DSL configurations are covered side by side throughout. If you need a SonarQube instance to connect to first, see our guide on SonarQube alternatives to understand your hosting options, or jump straight to the SonarQube tool page for an overview of features and pricin