Understanding New Code in SonarQube Server

Overview

This course guides you through the strategic importance of the "New Code" period in SonarQube Server and teaches you how to configure it to maintain integrated code quality and security. You will learn how to focus your development efforts on recent changes rather than being overwhelmed by legacy technical debt.

Learning objectives

• Explain the importance of focusing on new code to maintain integrated code quality and security

• Identify the different methods SonarQube Server uses to track new code

• Configure the New Code definition at the global, project, and branch levels

• Select the optimal New Code period based on your team's specific development lifecycle
  

Key topics

• The logic behind isolating recent changes to build a sustainable development process

• Methods for identifying new lines using SCM metadata and analysis dates

• New Code definition options including Previous version, Number of days, Reference branch, and Specific analysis

• Hierarchy and precedence of settings across global, project, and branch levels

• Best practices for baseline creation and quality gate behavior

Target audience

The target audience consists of software developers, DevOps engineers, and SonarQube administrators who are responsible for managing code quality and security within their repositories. Based on the content's focus on configuration levels and development lifecycles, it is inferred that the course is designed for professionals who need to align automated code analysis with specific team workflows, such as traditional release cycles or continuous delivery.

Prerequisites

• Access to a SonarQube Server instance

• Basic understanding of Source Code Management (SCM) data, specifically Git

• Familiarity with CI/CD environments and scanner configurations

• Knowledge of project build systems like Maven or Gradle for version detection