Configuring new code calculation

Configuring your project’s new code definition.

By default, your project applies the baseline for new code (global-level new code definition). This means it consistently uses the baseline for new code. Consequently, any modifications to the baseline will automatically be applied to your project. You can apply a specific new code definition for your project instead.

For more information, see Quality standards and new code.

Setting a specific new code definition for your project

As a project administrator, you can set the new code definition for your project in the UI (except the Specific analysis option) or using the Web API, at creation time or anytime later as explained below.

For more compliance with the Clean as You Code methodology, the Specific analysis option can only be set using the Web API, as it would require frequent user action to be kept up to date.

In the UI

To set a specific new code definition for your project in the UI:

  1. Retrieve your project. See Retrieving projects for more details.

  2. Go to Project Settings > New Code.

  3. In Choose the baseline for new code for this project, select Define a specific setting for this project and then the option you want to apply to your project.

Via the Web API

Use the api/new_code_periods/set endpoint.

Additional setup and recommendations

Make sure to follow the recommendations about the Checked-out code and SCM integration.

We also recommend completing your merges using the fast-forward option without a merge commit; examples include GitHub’s squash and merge or rebase and merge options. That way, blame for merged commits will always have a more recent commit date.

If using Previous version option

The current version of a project is determined in different ways depending on the build system:

  • If the analysis is done using the SonarScanner for Maven, then SonarQube Community Build reads the version from the pom.xml file.

  • If the analysis is done with the SonarScanner for Gradle then SonarQube Community Build reads the version from the build.gradle file.

  • In all other cases, you must explicitly specify the version by setting the analysis parameter sonar.projectVersion.

Last updated

Was this helpful?