How is code quality control organized?

Code quality control is usually organized through several levels:

• Code Review — a mandatory stage where colleagues check changes before merging into the main branch. This helps identify errors, improve readability, and architecture.
• Automated tests — unit tests, integration tests, and e2e tests that run in CI/CD and ensure that functionality is not broken.
• Static code analysis — tools like SonarQube, Checkstyle, PMD that check style, potential bugs, and vulnerabilities.
• Test coverage — metrics showing how much of the code is covered by tests, helping to maintain quality.
• Adherence to coding style — uniform formatting and naming rules, often automated through linters.

Example of a check configuration in Jenkins Pipeline:

pipeline {
    stages {
        stage('Build') {
            steps {
                sh './gradlew build'
            }
        }
        stage('Test') {
            steps {
                sh './gradlew test'
            }
            post {
                always {
                    junit '**/build/test-results/test/*.xml'
                    recordIssues tools: [checkStyle(pattern: '**/build/reports/checkstyle/*.xml')]
                }
            }
        }
        stage('Code Review') {
            steps {
                // Usually a manual stage or integration with GitHub Pull Requests
            }
        }
    }
}