90+ SonarQube Interview Questions and Answers (2027)

92 SonarQube interview questions with answers: quality gates, profiles, new code, hotspots, MQR mode, Jenkins and GitHub Actions, scenarios.

Sep 26, 2025 - 10:57
Nov 11, 2026 - 12:25
 0  157
90+ SonarQube Interview Questions and Answers (2027)

SonarQube interview questions check whether you can set up static code analysis and make it useful in CI/CD: how the server and scanners work, how quality profiles and quality gates decide pass or fail, what "new code" means, how security hotspots differ from vulnerabilities, and how to wire SonarQube into Jenkins, GitHub Actions or GitLab. This page has 92 questions with direct answers.

Answers were checked against the SonarQube Server documentation (2026.x releases) in November 2026. Product names follow Sonar's 2024 rebrand: SonarQube Server, SonarQube Cloud (formerly SonarCloud), SonarQube Community Build (formerly Community Edition) and SonarQube for IDE (formerly SonarLint). For where code analysis sits in a pipeline, see our guide to CI/CD quality gates.

Key takeaways

  • Freshers are asked what SonarQube measures (reliability, security, maintainability, coverage, duplication), how scanners send results and what a quality gate is.
  • Mid-level candidates should configure scanners for Maven, Gradle, .NET or the CLI, tune quality profiles, define new code and fail a pipeline on a red gate.
  • Senior rounds cover deployment (database, Elasticsearch requirements, Data Center Edition), upgrades on the LTA track, branch and pull request strategy and governance across hundreds of projects.
  • SonarQube Server can run in Multi-Quality Rule (MQR) mode or Standard Experience. MQR uses Blocker, High, Medium, Low and Info severities; Standard Experience uses Blocker, Critical, Major, Minor and Info with bug, vulnerability and code smell types.
  • Community Build analyses the main branch only. Branch analysis and pull request decoration need a commercial edition or SonarQube Cloud.

How this SonarQube guide is organised

This is the main SonarQube question bank on the site. For short definitions aimed at freshers, read the most asked SonarQube questions. For troubleshooting drills, the scenario-based SonarQube questions go further, and the advanced SonarQube questions cover architecture.

ProductFormer nameHostingBranch and PR analysis
SonarQube Community BuildCommunity EditionSelf-managedMain branch only
SonarQube Server (Developer, Enterprise, Data Center)SonarQube editionsSelf-managedYes
SonarQube CloudSonarCloudSaaSYes
SonarQube for IDESonarLintIDE pluginLocal analysis, connected mode

SonarQube interview questions for freshers

1. What is SonarQube?

SonarQube is a code quality and code security platform from SonarSource. It runs static analysis on source code, reports issues, coverage and duplication, and decides through a quality gate whether code is fit to merge or release.

2. What is static code analysis?

Examining source code without running it to find bugs, security weaknesses and maintainability problems. SonarQube applies thousands of language-specific rules to the code's syntax tree and data flow.

3. What does SonarQube measure?

Issues affecting the three software qualities (security, reliability and maintainability), security hotspots, test coverage (imported from your test tools), duplicated code, size and complexity.

4. What are the main components of SonarQube Server?

The web server (UI and API), the compute engine (processes analysis reports in the background), an embedded Elasticsearch search server, and an external database. Scanners run on build machines and send reports to the server.

5. What is a scanner?

The client that analyses code on the build machine and uploads a report. Options include SonarScanner CLI, SonarScanner for Maven, for Gradle, for .NET and for npm, plus CI integrations for Jenkins, GitHub Actions, GitLab CI/CD, Azure Pipelines and Bitbucket Pipelines.

6. Which port does SonarQube use by default?

Port 9000 for the web UI and API. Change it with sonar.web.port in sonar.properties. In production it usually sits behind a reverse proxy serving HTTPS.

7. Which databases are supported?

PostgreSQL, Microsoft SQL Server and Oracle. The embedded H2 database is only for evaluation and cannot be upgraded or used in production. Check the requirements page for supported versions of your release.

8. What is a quality profile?

A set of rules activated for one language. Each project uses one profile per language. The built-in profile is called "Sonar way"; teams extend it or copy it to add or remove rules.

9. What is a quality gate?

A set of conditions that a project analysis must meet, such as no new issues or at least 80% coverage on new code. The gate returns Passed or Failed, and CI pipelines use that result to block merges or releases.

10. What conditions does the built-in "Sonar way" quality gate use?

It focuses on new code: no new issues, all new security hotspots reviewed, coverage on new code of at least 80%, and duplication on new code of at most 3%. Check your version's gate page, since defaults can change between releases.

11. What is "new code" in SonarQube?

The code changed within the new code period you define, for example since the previous version, in the last 30 days, or compared with a reference branch. Gates focus on it so teams fix what they touch instead of the whole legacy codebase at once.

12. What is a security hotspot?

Security-sensitive code that needs a human review, such as a hard-coded IP, a weak cookie setting or use of a cryptographic API. It is not confirmed as a vulnerability; a reviewer marks it Safe, Fixed or Acknowledged.

13. How is a vulnerability different from a security hotspot?

A vulnerability is an issue SonarQube is confident needs fixing. A hotspot depends on context, so SonarQube asks a person to decide. Both affect the security view, but they are reviewed in different places.

14. What are reliability, security and maintainability ratings?

Letter grades from A (best) to E based on issue severity or, for maintainability, the technical debt ratio. They summarise a project's state and can be used as gate conditions.

15. What is technical debt in SonarQube?

The estimated time to fix all maintainability issues, based on a remediation effort assigned to each rule. The technical debt ratio compares that effort with the estimated cost to develop the code.

16. What is code duplication, and how is it measured?

Blocks of code repeated in several places. SonarQube reports duplicated lines, blocks and files, with the minimum block size depending on the language. Duplication makes fixes harder because each copy must be changed.

17. Does SonarQube run my tests?

No. Your build runs tests and a coverage tool such as JaCoCo, coverage.py, Istanbul or Coverlet writes a report. The scanner imports that report through properties such as sonar.coverage.jacoco.xmlReportPaths or sonar.python.coverage.reportPaths.

18. What is sonar.projectKey?

The unique identifier of a project on the server. It is required for every analysis, and changing it creates a new project instead of updating the old one.

19. What is a sonar-project.properties file?

The configuration file read by SonarScanner CLI from the project root.

sonar.projectKey=shop-api
sonar.projectName=Shop API
sonar.sources=src
sonar.tests=tests
sonar.exclusions=**/generated/**
sonar.python.coverage.reportPaths=coverage.xml

20. How does a scanner authenticate?

With a token generated in SonarQube, passed through the SONAR_TOKEN environment variable or the sonar.token property. Token types are user, project analysis and global analysis tokens; use the narrowest type that works.

21. What languages does SonarQube support?

Around 30 languages and frameworks, including Java, C#, JavaScript, TypeScript, Python, Go, PHP, Kotlin, Ruby, C and C++, plus IaC files such as Terraform, CloudFormation, Kubernetes manifests and Dockerfiles. Some languages, such as C and C++, need a commercial edition.

22. What is SonarQube for IDE?

An IDE plugin (formerly SonarLint) for VS Code, JetBrains IDEs, Eclipse and Visual Studio that shows issues while you code. In connected mode it uses the same rules and quality profile as your SonarQube server.

23. What issue statuses exist?

Issues move between Open, Accepted, False positive and Fixed. Accepted means the team agrees it is real but will not fix it now. Fixed is set automatically when a later analysis no longer finds the issue.

24. What is a false positive, and how do you handle it?

An issue that is not a real problem. Mark it False positive in the UI with a comment, so it stays closed on later analyses. If one rule produces many false positives, review whether it belongs in your profile.

25. What is the difference between SonarQube Server and SonarQube Cloud?

Server is self-managed: you run it, the database and upgrades. Cloud is Sonar's SaaS, integrated with GitHub, GitLab, Bitbucket and Azure DevOps, with no infrastructure to manage. Analysis concepts are the same.

26. What is SonarQube Community Build?

The free, self-managed edition that replaced Community Edition in late 2024. It is released monthly and analyses one branch per project, without pull request decoration or some advanced security features.

27. What are Multi-Quality Rule mode and Standard Experience?

Two ways a SonarQube Server instance classifies issues. MQR mode groups issues by the software quality they affect, and one rule can affect several qualities. Standard Experience uses the older bug, vulnerability and code smell types. Admins switch modes in General Settings.

28. What severities does SonarQube use?

In MQR mode: Blocker, High, Medium, Low and Info. In Standard Experience: Blocker, Critical, Major, Minor and Info.

29. What is cyclomatic and cognitive complexity?

Cyclomatic complexity counts independent paths through code. Cognitive complexity, created by SonarSource, measures how hard code is to understand, adding weight for nesting and breaks in linear flow. Rules flag functions above a threshold.

30. Where can you see analysis results?

In the project dashboard (gate status, new code and overall code), the Issues and Security Hotspots pages, the Measures page, pull request decoration in your Git platform, and the Web API for automation.

SonarQube interview questions for 2 to 5 years of experience

31. How do you analyse a Maven project?

mvn clean verify org.sonarsource.scanner.maven:sonar-maven-plugin:sonar \
  -Dsonar.projectKey=shop-api \
  -Dsonar.host.url=https://sonar.example.com

Set SONAR_TOKEN in the environment. Running verify first produces test results and the JaCoCo report the scanner imports.

32. How do you analyse a Gradle project?

Apply the org.sonarqube plugin in the build file, configure properties in a sonar block, and run ./gradlew test jacocoTestReport sonar with SONAR_TOKEN set.

33. How do you analyse a .NET project?

dotnet sonarscanner begin /k:"shop-api" /d:sonar.host.url="https://sonar.example.com" /d:sonar.token="$SONAR_TOKEN"
dotnet build --no-incremental
dotnet sonarscanner end /d:sonar.token="$SONAR_TOKEN"

The begin step hooks into the build, and the end step uploads results.

34. How do you integrate SonarQube with Jenkins?

Install the SonarQube Scanner for Jenkins plugin, register the server under system configuration, wrap the analysis in withSonarQubeEnv, and add a waitForQualityGate step. Configure a SonarQube webhook to Jenkins so the step gets the result.

stage('Sonar') {
  steps {
    withSonarQubeEnv('sonar') {
      sh 'mvn -B verify org.sonarsource.scanner.maven:sonar-maven-plugin:sonar'
    }
  }
}
stage('Quality gate') {
  steps {
    timeout(time: 10, unit: 'MINUTES') {
      waitForQualityGate abortPipeline: true
    }
  }
}

35. How do you fail a pipeline when the gate fails without Jenkins?

Set sonar.qualitygate.wait=true. The scanner then polls the server until the compute engine finishes and exits with an error if the gate fails. sonar.qualitygate.timeout sets how long it waits.

36. How do you integrate with GitHub Actions?

Use the official SonarSource/sonarqube-scan-action, pass SONAR_TOKEN and SONAR_HOST_URL as secrets, and check out with fetch-depth: 0 so blame data and new code detection work. Maven, Gradle and .NET projects use their own scanners in a run step instead.

37. Why does shallow cloning cause problems?

SonarQube uses SCM blame to assign issues to authors and to detect new code. A shallow clone lacks history, so issues may be attributed wrongly or new code may be miscounted. Fetch full history for analysis jobs.

38. How do you integrate with GitLab CI/CD?

Configure the GitLab integration in SonarQube, add SONAR_TOKEN and SONAR_HOST_URL as masked CI/CD variables, run the scanner in a job with GIT_DEPTH: "0", and with a commercial edition merge requests get decorated with gate results.

39. What is pull request decoration?

SonarQube posts the gate status and new issues on the pull request in GitHub, GitLab, Bitbucket or Azure DevOps. Combined with branch protection, it blocks merges that fail the gate. It needs Developer Edition or above, or SonarQube Cloud.

40. How do you choose a new code definition?

Use "previous version" for projects with numbered releases, "reference branch" for teams that merge feature branches into main, and "number of days" for continuous delivery without versions. Set it at instance level and override per project when needed.

41. How do you exclude files from analysis?

Use sonar.exclusions for files that should not be analysed at all (generated code, vendored libraries), sonar.coverage.exclusions for files that should not count toward coverage, and sonar.cpd.exclusions for duplication. Prefer project settings in the UI so exclusions are visible.

42. How do you create a custom quality profile?

Copy or extend "Sonar way", activate or deactivate rules, change severities where your policy needs it, then set the profile as default for the language or assign it to specific projects. Extending keeps you in sync with new rules added to the parent.

43. Should you copy or extend a profile?

Extending inherits rule changes from the parent when SonarQube upgrades, so new rules arrive automatically. Copying freezes the rule set, which gives control but means you must add new rules yourself.

44. How do you write a custom quality gate?

Create a gate, add conditions on new code metrics (issues, hotspots reviewed, coverage, duplication, ratings) and optionally on overall code, and assign it to projects. Keep conditions few and focused on new code so teams can actually meet them.

45. Why should gates focus on new code?

Failing every build on legacy issues teaches people to ignore the gate. Requiring clean new code stops the debt growing, and the overall codebase improves as files are touched. Sonar calls this the Clean as You Code approach.

46. How do you handle coverage for a multi-module project?

Generate an aggregated coverage report (for example with JaCoCo's report-aggregate goal) or point the scanner at each module's report. Coverage of 0% usually means the report path is wrong or the report was produced after the scan.

47. What is taint analysis?

Data flow analysis that tracks untrusted input from sources (such as HTTP parameters) to sensitive sinks (SQL queries, file paths, OS commands) across methods and files. It finds injection vulnerabilities and is available in commercial editions.

48. What are webhooks used for?

SonarQube calls a URL when the compute engine finishes processing an analysis, sending the gate status. Jenkins' waitForQualityGate and other automation use them. You can set a secret to sign the payload.

49. How do you use the SonarQube Web API?

Call REST endpoints with a token, for example api/qualitygates/project_status?projectKey=shop-api for the gate result, api/issues/search for issues, or api/measures/component for metrics. The API documentation is built into every instance.

50. How do you analyse infrastructure as code?

SonarQube includes rules for Terraform, CloudFormation, Kubernetes YAML, Helm, Ansible, Docker and others. Include those files in sonar.sources and they are analysed in the same run, which catches issues like public storage or containers running as root.

51. What is SonarQube's secrets detection?

Rules that flag hard-coded credentials such as cloud access keys, tokens and private keys in code and configuration files. It complements, but does not replace, pre-commit secret scanning and secret managers.

52. How does connected mode help developers?

SonarQube for IDE downloads the project's quality profile and accepted or false-positive decisions from the server, so developers see the same issues locally that the pipeline will report and can fix them before pushing.

53. What are permission templates?

Templates that set default permissions for new projects, optionally matched by project key pattern. They make sure every new project gets the right groups for browse, execute analysis, administer issues and administer settings.

54. How do you integrate authentication?

SonarQube supports LDAP, SAML and the DevOps platform logins (GitHub, GitLab, Bitbucket and Azure DevOps), with group synchronisation for some. Disable the built-in admin password reuse and enforce authentication with sonar.forceAuthentication (enabled by default in recent versions).

55. What is the difference between overall code and new code on the dashboard?

Overall code shows the state of the whole project. New code shows only what changed in the new code period. Gates normally evaluate new code, while overall ratings track long-term health.

56. What is AI CodeFix?

A SonarQube Server and Cloud feature that uses a large language model to suggest fixes for some issues in the UI and IDE. It is optional and controlled by admins. Review suggested fixes like any other code change.

57. What is AI Code Assurance?

A feature that lets you mark projects containing AI-generated code and apply a stricter quality gate to them. Check your edition's documentation for availability.

58. How do you report coverage for JavaScript or TypeScript?

Run tests with a tool that writes LCOV, such as Jest or Vitest with coverage enabled, and point sonar.javascript.lcov.reportPaths at the lcov.info file.

Senior SonarQube interview questions

59. How do you size and deploy SonarQube Server for production?

Run it on a dedicated host or Kubernetes with an external PostgreSQL (or other supported database), fast local disk for Elasticsearch indexes, and enough memory for the web server, compute engine and search processes. Put HTTPS in front with a reverse proxy and back up the database.

60. What host settings does Elasticsearch need on Linux?

The docs require vm.max_map_count of at least 524288 and fs.file-max of at least 131072, plus enough open file descriptors and threads for the SonarQube user. Without them the search process fails to start.

sysctl -w vm.max_map_count=524288
sysctl -w fs.file-max=131072

61. Can you run SonarQube on Kubernetes?

Yes. Sonar publishes official Helm charts for SonarQube Server and for Data Center Edition. Use a persistent volume, an external database, an init container or node settings for vm.max_map_count, and set resource requests generously.

62. What is Data Center Edition?

The high-availability edition. It runs several application nodes behind a load balancer and a separate cluster of search nodes, sharing one database, so a node failure does not stop the service.

63. How do you upgrade SonarQube safely?

Read the release upgrade notes, back up the database, test the upgrade on a copy, upgrade plugins, then start the new version and open /setup to migrate the database. Follow the documented upgrade path through LTA versions when jumping several releases.

64. What is an LTA release?

A Long-Term Active release of SonarQube Server that receives fixes for an extended period, for teams that cannot upgrade often. Since 2025 Server versions follow a year-based scheme such as 2025.1. Community Build follows its own monthly cycle without LTA.

65. How do you manage quality standards across hundreds of projects?

Keep a small number of company quality profiles that extend "Sonar way", one default gate plus a stricter one for critical systems, permission templates by key prefix, and automation through the Web API or Terraform providers. Review rule changes in a central group.

66. How would you roll SonarQube out to a large codebase with years of debt?

Start with analysis only, no blocking. Set a sensible new code period, apply a new-code gate, enable PR decoration, then switch on blocking per team once they pass regularly. Do not ask teams to fix all legacy issues first.

67. How do you handle monorepos?

Create one SonarQube project per deployable component, scope each with sonar.sources and project key, and run only affected analyses in CI. Enterprise Edition adds monorepo support for PR decoration across several projects in one repository.

68. What are portfolios and applications?

Enterprise Edition features that aggregate projects. An application groups the projects that make up one product; a portfolio rolls up many projects or applications for management reporting on ratings and gate status.

69. How does SonarQube fit into a DevSecOps toolchain?

It covers SAST, code quality, IaC and secrets rules in pull requests. You still need software composition analysis for dependencies, container image scanning, DAST against running apps, and runtime monitoring. SonarQube Advanced Security adds dependency analysis in recent Server versions; check your edition.

70. How do you keep analysis fast on large projects?

Analyse only real source paths, exclude generated and vendored code, give the scanner enough memory, use the analysis cache that SonarQube provides for PRs, and run the compute engine with enough workers (Enterprise and Data Center allow several).

71. How do you measure whether SonarQube is improving quality?

Track the share of PRs passing the gate on the first try, new issues per change, ratings trends on overall code and time to review hotspots. Pair those with defect and incident data, because a passing gate is a proxy, not proof.

72. What are the risks of making the gate too strict?

Teams start marking real issues as false positives, excluding files or bypassing the pipeline. Keep conditions achievable, explain every rule change, and watch for rising false-positive and accepted counts as a warning sign.

73. How do you secure the SonarQube instance itself?

Force authentication, use SSO, remove the default admin credentials at first login, use project analysis tokens instead of user tokens in CI, rotate tokens, restrict network access, keep plugins to a minimum and patch regularly.

74. How do you back up and restore SonarQube?

Back up the database with its native tools. Elasticsearch indexes are rebuilt from the database on start-up, so you do not need to back up the data/es directory. Keep a copy of sonar.properties and installed plugins too.

75. How would you compare SonarQube with other SAST tools?

SonarQube combines code quality and security in one gate and is strong on developer workflow. Tools such as Semgrep, CodeQL, Checkmarx or Snyk Code may offer deeper or custom security rules. Many teams run SonarQube for quality and gates and add a specialised security scanner.

76. How do you treat issues raised on AI-generated code?

The same way as any other code: the gate applies to new code regardless of who wrote it. Mark projects that use AI assistants heavily, apply a stricter gate if your policy needs it, and keep human review of hotspots.

Scenario-based SonarQube interview questions

77. Coverage shows 0% even though tests pass. What do you check?

Confirm a coverage report was generated before the scan, the report path property points to the right file, the format matches the property (for example JaCoCo XML, not the binary file), and paths inside the report match the source paths SonarQube analyses.

78. The quality gate fails on code nobody touched. Why?

The new code period may be wrong, for example a "previous version" that never changed so everything counts as new, or a shallow clone breaking blame data. Fix the new code definition and fetch full Git history.

79. waitForQualityGate times out in Jenkins. What is wrong?

The SonarQube webhook to Jenkins is missing or unreachable, so Jenkins never hears the result. Configure the webhook to https://jenkins.example.com/sonarqube-webhook/, check firewall rules, and check the compute engine queue for a backlog.

80. SonarQube will not start after a host reboot. Where do you look?

Read logs/sonar.log, es.log, web.log and ce.log. A common cause is vm.max_map_count reverting because it was not persisted in /etc/sysctl.d. Others are database connection failures or a full disk.

81. Developers complain a rule gives many false positives. What do you do?

Check examples to confirm, report it to Sonar if it is a real false positive, and decide as a team whether to deactivate the rule in your profile or lower its severity. Do not exclude whole files to silence one rule.

82. A pull request shows no SonarQube comment. Why?

Community Build does not support PR decoration. With a commercial edition, check the DevOps platform integration settings, that the scanner passed PR parameters (CI integrations usually do this automatically), and that the token has permission to comment.

83. Analysis runs for 40 minutes. How do you speed it up?

Exclude generated, vendored and test fixture files, check that the scanner is not analysing node_modules or build output, increase scanner memory, and look at the compute engine queue. For C and C++, make sure the build wrapper or compilation database is set up correctly.

84. A hard-coded AWS key was flagged in a merged commit. What is the response?

Treat it as an incident: revoke and rotate the key in AWS first, check CloudTrail for use, remove the secret from code and move it to a secret manager, then add pre-commit secret scanning. Marking the issue fixed in SonarQube is the last step.

85. Two teams share a project key by mistake. What happens and how do you fix it?

Each analysis overwrites the other's results, so history and gate status are meaningless. Give each component its own key, re-run analysis, and delete or archive the mixed project. Use a key naming convention to prevent repeats.

86. The database grew very large. What can you do?

Adjust housekeeping settings to delete old analyses, inactive branches and closed issues sooner, delete abandoned projects, and run database maintenance (for PostgreSQL, vacuum and analyse). Check that short-lived branches are cleaned up.

87. Management wants zero issues across the whole codebase within one quarter. How do you respond?

Explain the cost and risk of large clean-up changes, propose a new-code gate so debt stops growing, and agree a targeted plan for high-severity security and reliability issues in critical services. Show progress with ratings trends.

88. A security hotspot was marked Safe but caused an incident. What changes?

Review who can mark hotspots, require a second reviewer for certain categories, record reasoning in comments, and train reviewers on that category. Add tests or a rule for the specific pattern if one exists.

89. After switching to MQR mode, issue counts rose and gates failed. Why?

In MQR mode one issue can affect several software qualities, so counts per quality may go up, and gate conditions written for the old types may behave differently. Review and update gate conditions after changing mode.

90. Scanner fails with "Not authorized" in CI. What do you check?

That SONAR_TOKEN is set in the job, has not expired or been revoked, has Execute Analysis permission on the project, and that the job targets the right sonar.host.url. Project analysis tokens work only for their own project.

91. You need to migrate from SonarQube Server to SonarQube Cloud. How do you plan it?

Inventory projects, profiles and gates, recreate custom profiles and gates in Cloud, bind repositories through the Git platform integration, update CI to use Cloud's URL and tokens, and run both in parallel for a period. Issue history and review decisions need special handling, so check Sonar's migration guidance.

92. Quality gate passes but production bugs keep appearing. What does that tell you?

Static analysis catches only some defect types. Check coverage quality (tests that assert behaviour, not just run lines), add integration tests and runtime monitoring, and look at whether the bugs match rules that are inactive in your profile.

How to prepare for a SonarQube interview

  1. Run SonarQube Community Build with Docker and PostgreSQL and analyse one Java or Python project with coverage.
  2. Build a Jenkins or GitHub Actions pipeline that fails on a red quality gate.
  3. Create an extended quality profile and a custom gate, then explain each condition.
  4. Practise explaining new code periods and why they change gate results.
  5. Know where SonarQube fits next to dependency scanning, image scanning and DAST, as covered in our DevSecOps tools guide.

Our DevSecOps training includes SonarQube in CI/CD pipelines, in the Kharadi, Pune classroom and live online. For pipeline questions around it, see the Jenkins interview questions and the DevOps interview questions hub.

Frequently asked questions

Is SonarQube free?

SonarQube Community Build is free and self-managed, with main branch analysis only. SonarQube Server editions (Developer, Enterprise, Data Center) and SonarQube Cloud paid plans add branch and PR analysis and more security features. SonarQube Cloud also has a free tier.

What is the difference between a quality profile and a quality gate?

A quality profile decides which rules run for a language. A quality gate decides whether the analysis result passes, using conditions such as new issues, coverage and duplication.

What is the default SonarQube port?

Port 9000. You can change it with sonar.web.port and usually put an HTTPS reverse proxy in front.

Can SonarQube replace code review?

No. It catches rule-based problems automatically so reviewers can spend time on design and logic. Security hotspots in particular need a human decision.

What happened to SonarCloud and SonarLint?

In late 2024 Sonar renamed SonarCloud to SonarQube Cloud, SonarLint to SonarQube for IDE, SonarQube editions to SonarQube Server, and Community Edition to SonarQube Community Build.

Does SonarQube support pull request analysis in the free version?

No. Community Build analyses one branch per project. Branch and pull request analysis need Developer Edition or higher, or SonarQube Cloud.

Which coverage tools work with SonarQube?

Any tool that writes a supported report format, such as JaCoCo for Java, coverage.py for Python, LCOV from Jest or Vitest for JavaScript, and Coverlet or dotCover for .NET.

References

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.