Quality standards and new code

Improve code quality by focusing on new code and applying consistent quality standards. This page is for SonarQube 8.9.

For AI agents: You're in the SonarQube Server 8.9 documentation. For a list of all 8.9 pages, see the SonarQube Server 8.9 page index. For the whole site, see the page index or the full text. For another version, replace 8.9 in the URL with that version. The latest version has no version number in its URL.

Defining a quality standard

SonarQube helps you improve code quality by focusing on new code and applying consistent quality standards. As a developer, you focus on maintaining high standards for the code you add or change. SonarQube gives you the tools to enforce those standards and take pride in shipping maintainable and secure code.

Understanding the benefits of focusing on new code

To get a visual representation of the benefits of focusing on new code based on the data in your projects:

1. Download and install the Clean as You Code stats plugin.
2. In SonarQube, navigate to More > Clean as You Code.

Focus on new code

By focusing on Defining New Code (code that has been added or changed according to your new code definition), you can make sure the code you write today is maintainable and secure.

The Defining New Code definition can be set at different levels (global, project, and, starting in Developer Edition, at the branch level). Depending on the level at which your new code definition is set, you can change the starting point to fit your situation.

For more information on setting your Defining New Code, check out https://app.gitbook.com/s/okrRDNmcwFJDrkLkn0sz/project-administration/defining-new-code.

Personal responsibility

By focusing on new code, you aren’t responsible for anyone else’s code. You own the quality and security of the code you are working on today. If you add new issues, SonarQube automatically assigns them to you so you can maintain the quality of your code.

For more information on issues and how they are assigned, check out the Issues page.

Quality gate

Your Quality gates is a set of conditions that tells you whether or not your project is ready for release. To support improving code quality, your quality gate should:

• Focus on New code metrics – When your quality gate is set to focus on new code metrics (like the built-in Sonar way quality gate), new features will be delivered cleanly. As long as your quality gate is green, your releases will continue to improve.
• Set and enforce high standards – When standards are set and enforced on new code, you aren’t worried about having to meet those standards in old code and having to clean up someone else’s code. You can take pride in meeting high standards in your code. If a project doesn’t meet these high standards, it won’t pass the quality gate, and is therefore not ready to be released.

For more information on quality gates and to make sure your quality gate is enforcing your standards, check out the https://app.gitbook.com/s/okrRDNmcwFJDrkLkn0sz/user-guide/quality-gates page.

Pull request analysis

You can use pull request analysis and pull request decoration to make sure that your code meets your standards before merging. Pull request analysis lets you see your pull request’s quality gate in the SonarQube UI. You can then decorate your pull requests with SonarQube issues directly in your DevOps platform’s interface.

For more information on setting up pull request analysis and pull request decoration, see the documentation onPull request analysis.