O'Reilly logo

Continuous Integration, Delivery, and Deployment by Sander Rossel

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Leak periods

The last thing I wish to discuss relating to SonarQube is the so-called leak period. The leak period is basically a time frame in which you monitor new code. Let's say the leak period is a week. Within that week, the code smells, bugs, and technical debt are measured and accumulated. After a week, you start fresh, but keep track of how much smells, bugs, and debt was added since the last leak period. Your issues do not go away, but there were no issues added since the last leak period. This strategy is especially useful for legacy projects; projects that did not use SonarQube before and projects that just have been ignored in SonarQube. For such projects, especially if they are big, you may have a year worth of technical debt. ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required