Tell me about quality gates: why did you build them, what did you implement?

Quality gates are a set of criteria and checks that code must pass before entering the main branch or production. They help maintain product quality and prevent bugs.

Typically, when establishing quality gates, the following are implemented:

• Automatic execution of unit tests and integration tests.
• Code coverage analysis.
• Static code analysis (lint, SonarQube) to identify potential errors and quality issues.
• Code style compliance checks.
• Security checks (e.g., vulnerability scanning).

Implementing quality gates allows for:

• Early defect detection.
• Increased stability and reliability of releases.
• Improved code readability and maintainability.

For example, in a Jenkins pipeline, steps are added to run tests and code analysis, and if they fail, the build does not continue and merging into the main branch does not occur.