CodeScene has a new Continuous Integration feature. Delta analysis can provide warnings about high risk commits.
CodeScene lets you uncover and prioritize code that’s hard to maintain or parts of the code that become team productivity bottlenecks.
As such the techniques are reactive. Wouldn’t it be great if we could catch such problems much earlier, ideallybeforethey are even delivered to our main branch?
In this blog post we explore a new feature of CodeScene that turns the analyses into a pro-active tool for early feedback. You’ll see how CodeScene offers the ability to detect maintenance problems and early warnings in your codebase by integrating the analysis results into your build pipeline and/or as robot comments in a code review tool like Gerrit.
Fight reviewer fatigue
The challenge with all preventive and corrective techniques is that they require time and discipline. Let’s take code reviews as an example. Code reviews done right are a proven defect removal technique. A code review is also an opportunity for knowledge sharing and learning. However, none of those benefits come for free.
Like all manual processes code reviews are hard to scale. As your organization grows, code reviewer fatigue becomes a real thing; There’s just so many lines of code you can review each day. Beyond that point you’re likely to slip. The result is increased lead times, bugs that pass undetected to production, and – in extreme cases – the risk for burnout.
At Empear we’ve developed a system for automated risk classifications to prioritize the code we need to review. The risk classification is built into CodeScene, which exposes a REST API that lets you integrate the classification into your continuous integration pipeline. The following figure shows an example from a Jenkins build:
Adam Tornhill is a programmer who combines degrees in engineering and psychology. He’s the founder and CTO of CodeScene where he designs tools for code analysis. Adam is also a recognized international speaker and the author of multiple technical books, including the best selling Your Code as a Crime Scene and Software Design X-Rays. Adam’s other interests include modern history, music, retro computing, and martial arts.
Subscribe to our newsletter
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Semper neque enim rhoncus vestibulum at maecenas.
Ut sociis dignissim.
Latest Articles
Change coupling: visualize the cost of change
Code can be hard to understand due to excess accidental complexity. Or, it can look simple, yet its behavior is anything but due to complex...
CodeScene's IDE Extension brings CodeHealth™ Analysis directly into your editor
We've just launched an IDE Extension for VS Code, helping developers tackle code complexity within the editor. Read more and try it out!
Example of a functional programming refactoring pattern
In this post we'll demonstrate an example of a functional refactoring pattern.