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

Deploying the checker package to the Server and build machines

To deploy a custom checker, you must install the checker package on the Klocwork Server and on each build machine:

  1. Copy the checker package zip file to the projects_root/plugins directory for the Klocwork Server, creating the directory if it doesn't already exist.

    If the C/C++ checker is platform-specific, copy the zip file to projects_root/plugins/<platform-name>. See Deploying custom checkers for a list of platform names.

    If you are deploying a C# checker, copy the zip file to projects_root/plugins/csharp.

  2. Wait 30 seconds to ensure the system updates the list of checkers.
  3. Deploy the new checker to the Server by running the kwdeploy sync command with the --url option, specifying the Klocwork Server host machine:
    kwdeploy sync [--url http(s)://<host>:<port>]
    
    The system adds the checker to the <server-install>/plugins directory.
  4. On each build machine, run the kwdeploy sync command with the --url option, specifying the Klocwork Server host machine:
    kwdeploy sync [--url http(s)://<host>:<port>]
    
    Note: If you don't see a message that states that the directory was updated, run the command again.
  5. Run an integration-build analysis with kwbuildproject:
    kwbuildproject --tables-directory <dir> [<options>] <build_specification> 
    
  6. Have connected desktop users synchronize with the Klocwork Server by running a desktop analysis in their IDE or by using kwcheck.
Tip: Add the kwdeploy sync command with the --url option to the top of your build script to automate this process and ensure that your build machines are always in sync with the Server.