Static-code analysis tools provide a wealth of information about your code, and highlight numerous opportunities for improvement. If you are like most teams, however, you are rarely given a block of dedicated time to devote to this technical debt, and therefore critical opportunities get lost in the information overload of the analysis results. The most opportune time to identify and act on coding issues is as they are being introduced. In this session, you will learn how to leverage your automated build to monitor your analysis results, and to immediately act on impacted areas that are most important to you. For example, you will learn how to leverage your build to detect duplication introduced into the code base, a change to an area of known complexity, or matches on keywords frequently linked to defects. You will then learn how to have the build automatically initiate a code review in response to these findings. This session will also highlight additional opportunities to leverage code analysis in your build such as automating the generation of release notes, and automating the maintenance of a web-service catalog. The discussion will cover both custom tools and techniques, as well as identifying opportunities to leverage and integrate off-the-shelf products.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.