Analyzers in the pipeline
Your code-quality analyzers run as a governed step in the same pipeline that ships the code.
Quality
Code Quality
Gate on maintainability, coverage, and duplication you can see
Bring your code-quality analyzers into the pipeline and gate on signals like maintainability, coverage, and duplication. Findings are normalized alongside the rest of your release evidence so quality lives next to everything else. This is an emerging capability under active development that orchestrates the analyzers you run.
- Quality signals are part of the release decision, not a report reviewed after the fact
- The same threshold rules apply across every team and pipeline, defined once as policy
- Quality findings sit alongside security and test results in one consistent release record
The problem
Your teams run code-quality analyzers, but the results rarely connect to the release decision. Maintainability scores, coverage numbers, and duplication counts land in separate reports that someone has to check manually. When that check gets skipped, a low-quality release ships without anyone knowing a threshold was crossed.
Without IntegraCI
- Analyzer output in reports that do not block releases
- Quality thresholds written in wikis, not enforced anywhere
- Coverage and duplication reviewed after the fact, if at all
- Each team wiring its own analyzer into its own pipeline
With IntegraCI
- Analyzers run as a governed step in the same pipeline that ships code
- Thresholds defined once as policy and evaluated at every release
- Quality findings normalized alongside security and test results
- One view of which quality signals a release met or missed
What you get
Gate on quality signals
Releases stop when maintainability, coverage, or duplication crosses the line you set.
Findings normalized
Quality findings land alongside security and test results in one consistent view.
Your analyzers, orchestrated
IntegraCI runs the analyzers your teams already trust rather than replacing them.
How it works
- 1
Connect analyzers
Point IntegraCI at the code-quality tools your teams run today.
- 2
Define the thresholds
You set the maintainability, coverage, and duplication limits a release must meet.
- 3
Gate and review
Findings flow into the release decision and into your normalized findings view.
How it stays governed
The same gates everyone passes, applied here.
Gated by policy
Quality thresholds are defined as policy as code and evaluated at every release gate. A release cannot proceed when maintainability, coverage, or duplication crosses the configured limit, regardless of which team or pipeline initiated it. The rules apply the same way everywhere because they are not embedded in any one team's pipeline YAML.
Recorded, tamper-evident
Every gate evaluation writes the outcome and the findings behind it once to a tamper-evident audit trail. You can show which quality signals a release met, which crossed the threshold, and why a build was blocked or allowed to proceed, with the evidence attached.
Works with your stack
Connect the tools you already run.
Code-quality analyzers are triggered by source control events, run within governed CI/CD pipeline steps, and their coverage and test signals feed the same release gate.
- Atlassian
- Gerrit
- Gitea
- GitHub
- GitLab
- Microsoft
- Akuity
- Amazon Web Services
- Buildkite
- CircleCI
- CNCF Tekton
- Drone CI
- Harness
- Jenkins
- Appium project
- Chaos Mesh
- Gatling Corp / open-source community
- Gretel.ai
- +5 more
Who it’s for
Where teams reach for it.
Enforce coverage gates before a release ships
You set a minimum coverage threshold as policy. Any release that falls below it stops at the gate before it reaches production, with the exact coverage figure recorded as part of the release evidence.
Standardize quality rules across many teams
When multiple teams run different analyzers, you define one shared threshold policy that applies at the release gate for all of them. Teams keep their existing tools; the quality rules become consistent across the organization.
Review quality findings next to security results
Maintainability and duplication findings flow into the same normalized view as security and test results, so reviewers see the full release picture in one place rather than switching between separate reports.
Questions, answered.
Does IntegraCI replace the analyzers we already run?
No. IntegraCI orchestrates the analyzers your teams already trust. Your tools keep running; IntegraCI governs the pipeline step they run in and evaluates their output against the thresholds you set.
Which code-quality tools can we connect?
IntegraCI is designed to work with the analyzers your teams already use. You point it at the tools you run today rather than adopting a new one. The catalog of supported integrations is growing as the capability matures.
How are thresholds defined and who controls them?
Thresholds are defined as policy as code by whoever you designate, such as a platform team or an engineering lead. Because they live as policy rather than in pipeline YAML, they apply consistently and cannot be silently overridden by a team editing their own pipeline file.
This is listed as an emerging capability. Is it ready to use?
The core flow, connecting analyzers, setting thresholds, and recording findings, is available. The capability is under active development, so the feature set will grow. Reach out to the IntegraCI team for current status and what is stable for your use case.
Put Code Quality on your stack.
Request a demo, or read the docs to see how it fits the tools you already run.