Use CodeScene's CI/CD Quality Gates to Manage Technical Debt with Positive Reinforcement
CodeScene identifies and prioritizes technical debt.
The earlier you can react to any potential finding, the better. That’s why CodeScene offers integration points that let you incorporate the analysis results into your build pipeline. In a CI/CD pipeline, CodeScene acts as an extra team member that predicts delivery risks and offers context-aware quality gates to supervise the health of your code.
Fixing technical debt and code quality issues is a hard problem. That’s why CodeScene goes beyond traditional quality gates and also reinforces positive behavior by providing feedback on code that improves its health. Let’s have a look at it in practice.
Meet the Quality Gates
CodeScene provides a simple REST API that lets you integrate the analysis results in a continuous integration pipeline and/or as robot comments in a code review tool like Gerrit. CodeScene maintains open-source integrations for the most popular platforms like Jenkins, GitLab, and GitHub.
In a build pipeline, performance is paramount; if the build is slow, the feedback loops break, and quality starts to slip one broken build after another. That’s why we made CodeScene fast. It just takes seconds to run a CI/CD analysis, so you can use it to get early feedback on a pull request or range of new commits. Let’s look at an example from a Jenkins pipeline: