Introducing Global Project Configuration: One Place to Manage All Your Qodana Rules

Kerry Beetge

Global Project Configuration is a new feature that helps Qodana users manage linter settings across an entire organization or team – all from one location. Until now, maintaining consistent code quality rules meant updating configuration profiles in every individual repository. 

Whether you were approving new licenses, adjusting rule severity, or defining custom patterns for hardcoded passwords, changes had to be repeated manually across multiple projects. However, as organizations scale, this approach becomes slow, error-prone, and difficult to audit.

Global Project Configuration solves this. It provides a streamlined, reusable, organization-wide mechanism for defining and enforcing code quality standards – without limiting the flexibility individual projects may need.

Book Demo

Why Global Project Configuration matters

With this new capability, you can:

• Establish organization-wide standards once, and apply them everywhere.
• Enforce best practices without sacrificing project-specific adjustments.
• Apply and update rules at scale, instantly affecting any linked projects.
• Reduce duplication and manual overhead, especially for large repositories or distributed teams.
• Improve consistency across teams, languages, and tech stacks.

This makes Qodana easier to manage, more adaptable to real-world work, and much more scalable.

How it works

Global Project Configuration is powered by a dedicated repository in which your organization stores the configuration files to be used during Qodana analysis. You can structure this repository in a way that suits your workflow, organizing configurations logically and referencing others to encourage reuse.

Configuring for teams: A practical example

Let’s look at how different teams might take advantage of this feature.

Imagine your organization creates a global Base configuration containing universal coding standards shared across all teams. From there:

Team A, which uses Lombok in Java development, inherits from Base and adds stricter Lombok-related rules. They apply this configuration only to their own projects.

Team B, maintaining a legacy project, inherits from Base but disables most checks except for security rules. This allows them to focus on critical issues without being overwhelmed by unrelated warnings.

Each team tailors the standards to their needs – while still aligning with the organization’s overall quality strategy.

Applying configurations to projects

Once a project is linked to a configuration:

• Qodana automatically applies it on the next run.
• Any changes pushed to the configuration repository are picked up and applied seamlessly.
• You can view all configurations and their associated projects in the Qodana Cloud UI, making management transparent and intuitive.

Everything is centralized, traceable, and easy to maintain.

Get started with Qodana’s Global Project Configuration

Visit Qodana Cloud → Settings → Global Configurations in the product, or view our documentation for a full guide on creating the configuration repository, syncing it with Qodana Cloud, and linking configurations to specific projects.

View Setup

Subscribe to Qodana Blog updates

Subscribe form

By submitting this form, I agree to the JetBrains Privacy Policy Notification icon

By submitting this form, I agree that JetBrains s.r.o. ("JetBrains") may use my name, email address, and location data to send me newsletters, including commercial communications, and to process my personal data for this purpose. I agree that JetBrains may process said data using third-party services for this purpose in accordance with the JetBrains Privacy Policy. I understand that I can revoke this consent at any time in my profile. In addition, an unsubscribe link is included in each email.

Submit

Thanks, we've got you!