The Qodana IntelliJ linter lets you perform a static analysis of your codebase and brings many of the smart features you’re familiar with from using the IntelliJ platform IDEs. It can:
- Improve your overall code structure
- Help you follow coding best practices
- Detect anomalous code and bugs
- Eliminate dead code
- Highlight spelling issues
Qodana in your CI
Use Qodana in any continuous integration system!
If your CI system’s user interface can be extended, the Qodana UI will integrate into it seamlessly. If not, you can expose the Qodana UI via a web server. For deeper integration, we will be providing dedicated plugins for various platforms.
Qodana can be launched in CI or locally as it is packed inside a Docker image.
The Qodana plugin for TeamCity lets you add static analysis to your build chain.
GitHub App and Actions
With the Qodana App and actions available on GitHub, static analysis can become an integral part of your repository.
License Audit with Qodana
Qodana specializes in build quality management, delivering the static analysis smarts of IntelliJ Platform to project-level checks. In May, we extended the platform with a second linter, Clone Finder, which detects code duplicates. Today, we are happy to announce the EAP for License Audit to detect incompatible third-party licenses on which your code relies, making the compliance verification process easier for your project and company.
Qodana Clone Finder: Early Access Program
Qodana helps you detect bugs without relying on an IDE, either on a local machine or a build server. It’s designed to seamlessly integrate into CI/CD pipelines. In addition to delivering static analysis for automated project-level evaluations, the Qodana team is developing additional audit features. One of them is Clone Finder, which finds duplicates in software repositories.
Early Access Program for Qodana, a New Product That Brings the “Smarts” of JetBrains IDEs Into Your CI Pipeline
JetBrains IDEs are well-known for their ability to understand code. They can track declarations, check references and types, and collect possible execution paths. Thanks to all this static analysis, you are able to rename and move things around safely, get appropriate code completion, and get warned with a message saying “hey, this won’t run” from the code inspection if you are adding something that won’t work into your code.