The question is typically phrased like this: how do I keep developers from checking in bad code? Usually the asker has in mind some automated check that prevents commits of code containing new issues.
Typically, he’s looking for a quick “turn on X” type of response, but the answer is more subtle and more powerful than that. Read the rest of this page »
Some people see rules – standards – requirements – as a way to hem in the unruly, limit bad behavior, and restrict rowdiness. But others see reasonable rules as a framework within which to excel, a scaffolding for striving, an armature upon which to build excellence. Read the rest of this page »
With SonarQube 4.3, the concept formerly known as alerts came into its own. No longer, a subset of Quality Profiles (it was always a slightly awkward fit there), the alert concept has grown up and become Quality Gates. Read the rest of this page »
