Every commit and every pull request, analysed
A dedicated, isolated cluster continuously analyses your code. It verifies builds, runs tests, checks dependencies and applies your standards, and among its outputs it surfaces rules-based findings into your own SonarQube or Qodana instance.
From a push to a result
Webhooks arrive from your source control and CI, orchestration schedules the work, and a cluster of workers carries it out. Every step is tracked, so nothing is analysed that you did not push.
Receive the event
Webhooks arrive from GitHub, GitLab, BitBucket and Azure DevOps, and from your CI, the moment code moves.
Fetch and diff
Repository content is pulled for the branch or pull request, and the change set is worked out so analysis focuses on what moved.
Build and test
The build is verified the way your teams run it, tests are executed, and code coverage is extracted.
Analyse
Your standards are applied and rules-based analysis runs, with findings surfaced into your own SonarQube or Qodana instance.
It builds your code the way your teams do
Analysis works against a real build. Qualimetry supports the common build engines, mobile builds, and reads code coverage in the formats your teams already produce.
- Common build engines including Ant, Gradle, Maven, MSBuild, and projects that need none.
- Mobile builds alongside your server and web projects, on the same cluster.
- Code coverage read in the common formats and carried through to your reporting.
A cluster that scales to your enterprise
Analysis runs on a dedicated, isolated cluster that scales for peak loads, so results keep up with every team even when the whole estate pushes at once.
- Dedicated and isolated so your code and your throughput are never shared.
- Scales for peak loads with more workers when the queue grows, fewer when it drains.
- Keeps up with every team so results land while the change is still fresh.
Many thousands of rules, across all your languages
Rules-based analysis combines Qualimetry's own rule packs with the SonarQube rules and other third-party analyzers, across Java, C#, JavaScript, TypeScript, Python and more. The findings surface into your own SonarQube or Qodana instance, deep-linked back to the standard that owns each rule.
Deep coverage
Qualimetry's own rule packs run alongside the standard analyzers, giving several times the depth of standard SonarQube for languages like Java and C#.
All your languages
One engine covers the mainstream languages your teams use, so governance and analysis stay consistent across the estate.
In your own instance
Findings are surfaced into your own SonarQube or Qodana instance, so your teams keep the tools they already work in.
Gate merges on quality and compliance
A merge check verifies that pull requests have passed their quality gates before they reach your long-lived branches, so problems are stopped at review rather than found in production.
Continuous analysis, answered
What triggers analysis?
Do you replace our SonarQube or Qodana?
Which build engines do you support?
Can it block merges?
See analysis running on your code
Book a demo to watch continuous analysis and merge gating against a real repository.