Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Setting up a post-checkin code review

To take full advantage of Code Review, you can build a revision history by importing any of your existing SCM revisions into your feed. Colleagues can also review any of these past revisions as necessary. To update Code Review with your SCM revision history, run a script to import the latest revisions using kwscm. You can trigger the script in any of the following ways:
  • a SCM commit hook
  • a continuous analysis build trigger (for example, a Jenkins post-commmit hook)
  • a scheduled task or cron job