Moving from SonarQube to Qodana
What a migration involves, from mapping quality profiles to running both tools side by side.
Read the articleYour team writes more code than it can review. Qodana checks every pull request before a person sees it, so reviewers spend their time on design and intent.
What is static code analysis?
Real screenshots of DSL.kt from the open-source awesome-kotlin project, on GitHub and in its public Qodana Cloud report, at commit 3d5c67a.
Many of the problems Qodana finds come with a fix. Qodana can apply those fixes in CI and open a pull request with them, so the developer checks a diff instead of making each change by hand.
Quick-fixes are deterministic. The same problem always gets the identical fix, on every run and every branch, with no AI guesswork.
Quick-fixes are included in Qodana Ultimate and Ultimate Plus.
Tell us where your team is starting from and we'll plan the rollout or migration with you.
Live reports from open-source projects, hosted on Qodana Cloud.
The same Qodana licences JetBrains sells, bought from an Australian JetBrains partner and supported by a team in Australia.
Support hours9am to 5pm, Monday to Friday
Supports most popular languages and development frameworks, as well as endless CI/CD integrations. Coverage is always expanding!
Is your technology missing? Contact us.
Guides and write-ups from the Adeptask team.
What a migration involves, from mapping quality profiles to running both tools side by side.
Read the articleWhy more generated code makes a deterministic check before review more valuable, not less.
Read the articleHow to switch on a quality gate without asking your team to clear years of technical debt first.
Read the articleAdding Qodana to an existing TeamCity pipeline and failing builds on new problems only.
Read the articleActive contributors, renewal dates and buying Qodana alongside your other JetBrains tools.
Read the articleStatic code analysis checks source code without running it. A tool reads every file against a defined set of rules and reports problems such as bugs, duplicated code, dead code and broken conventions.
Because it doesn't depend on a reviewer's time or attention, it gives the same result on every change. Qodana runs it in your CI on every pull request, before a person reviews the code.
Configuring Qodana linter profiles, mapping equivalent rules, and integrating Qodana into your CI/CD pipelines typically takes a few days to a week, depending on the size of your codebase.
Qodana is priced per active contributor, not on lines of code. Every plan analyses unlimited lines of code across unlimited projects.
An active contributor is anyone who has pushed a commit to a Qodana Cloud project in the last 90 days, and one licence covers them across every project. We quote in Australian dollars, so email us for a quote for your team.
Tell us how your team reviews code today. We'll demonstrate the advantage of a rollout or migration, and show you what Qodana can do for you.