Specify your project's build command. This command is used to compile the project and capture information about the build in a build specification file that Klocwork will use for the analysis.

The Klocwork tool used to generate the build specification, by default this is set to kwinject. Tools Available: kwinject monitors your C/C++ build to create a build specification kwmaven creates a Java build specification based on the information in your maven build file kwmavenw creates a Java build specification based on the information in your maven wrapper file kwjsspec creates a Javascript build specification file kwpyspec creates a Python build specification file kwant creates a Java build specification based on the information in your ant build file kwvcprojparser provides an alternative when kwinject cannot be used to create a build specification for a Microsoft Visual Studio 2012 or 2015 C/C++ project; however, it only provides results based on the previous generation (pre-Klocwork 2018) analysis engine kwcsprojparser creates a build specification for Visual Studio C# projects and solutions create tracefile uses kwinject to create a trace file, mainly used for debugging kwgradle creates a Java build specification based on the information in your Gradle build file kwgradlew creates a Java build specification based on the information in your Gradle wrapper file

Specify the build specification output filename and, optionally, its file path. By default, the build specification is written to kwinject.out in the current working directory. The specified file path can be absolute or relative to the workspace directory.

Specify other tool options here. Separate the options with whitespace; surround any arguments with whitespace in double quotes.

Ignore any error return codes from this step and continue.

Full integration analysis build failure conditions (Full)

Create multiple build failure conditions by using queries that are sent to the Klocwork Server through the Web API.

Filter issues based on the search query, then provide the status to set the build to, along with the threshold (the number of issues to meet this criteria).

Note: unless specified, the query runs with issue grouping turned off (grouping:off).

Differential analysis build failure conditions (CI)

Set a threshold for the differential analysis build failure conditions. Pass the build if the threshold is not exceeded; fail otherwise.

This step checks the XML report generated by the differential analysis build step. You can filter which issues appear in this report by providing additional options to the differential analysis build step.

This step counts the total number of issues in the XML report.

Build specification to use for analysis. Path is relative to the workspace

XML report file in which to store Klocwork results. Optional, in case you want to use the XML report for something custom; otherwise, a default file is created for the post-build step.

Additional options added to the kwciagent run command. For example, specify the number of jobs/threads to use (--jobs-num) or which filters to apply (--severity --taxonomy --system)

See the Klocwork documentation for more information.

Analyze changed files only

This feature allows for quick, incremental analyses of changed source files to enable pre/post-checkin/commit-like behavior . The goal is that only changed files are analyzed by the Klocwork kwciagent tool to replicate the local analysis developers would perform by using our supported IDE plugins or the command line utility. To enable this behavior, the plugin takes a list of the changed files from the SCM; this enables the system to analyze only the changed files when the workspace isn’t kept. Leave this cleared to analyze the whole project, or, if the workspace is kept, to perform a standard incremental analysis.

Diff file list

The diff file list is the file that contains the changed source files for Klocwork to analyze. All analyzed files must exist in the build specification generated by kwinject.

Note: All files to be analyzed must exist in the build specification.

Using Git

If using Git, provide the previous commit that Git should perform a "diff" against. The change list between the current commit and the specified previous commit will be added to the diff file list for Klocwork to process by automatically calling "git diff <previous_commit>" during the build. Note: If you are using Git jenkins plugin to obtain source files for you pipeline job be sure to use 'Pipeline script from SCM' and specify the previous commit with the environment variable, 'GIT_PREVIOUS_COMMIT'. Also be aware that the first build in the job won't be able to access GIT_PREVIOUS_COMMIT and the first build will run full CI analysis.

Manual

If you are not using Git, or want to manually generate the change list by using Git, select this option. You will need to generate the diff file list by using a custom build-step (or similar). List one changed source file on each line of the file.

Build specification to use for analysis. Path is relative to the workspace.

Specify the location of the tables directory, for example, ${MY_VAR}/kwtables.

Ignore compile errors encountered by kwbuildproject. This setting will not ignore a return code that indicates that kwbuildproject failed to the extent that no results are generated.

Optionally, provide configuration files to import to the project before running the analysis. If the checker configuration (for example, analysis_profile.pconf) is under version control, you can provide the file here and it will be automatically imported for each build.

Specify multiple files by separating them with commas (",").

By default, kwdeploy runs before the analysis, to ensure the checkers are up-to-date. Enable this setting if you don't want kwdeploy to run before the analysis.

Optional setting to specify the name of an existing Klocwork project. Klocwork will duplicate that project's configuration settings.

Enable to create a new Klocwork project on the server if one does not exist with the name specified. This can be useful when using multi-branch pipeline jobs.

Specify the name of the build for the Klocwork server, for example, ${MY_VAR}-${GIT_COMMIT}. If empty, Klocwork uses an auto increment to name the builds.

Cross synchronisation reads and writes to the Klocwork database. Therefore, we strongly recommend that you first try a Dry Run of the command (which skips the writing) and verify that the command works as expected.

Specify the "last synchronisation" date (how far back Klocwork should go when synchronising issue citations).

Format is "DD-MM-YYYY hh:mm:ss".

For example, "03-00-0000 00:00:00" will go back 3 days in time.

A regular expression that is used to retrieve Klocwork projects that should be processed during synchronisation. If you want to process all projects, leave empty.

For example, if you prepend projects with "DEPT-" to indicate a particular department the regular expression "^DEPT-" will match all these projects

Additional options added to the kwxsync command.

See the Klocwork documentation for more information.

Specify your project's build command. This command is used to compile the project and capture information about the build in a build specification file that Klocwork will use for the analysis.

The Klocwork tool used to generate the build specification, by default this is set to kwinject. Tools Available: kwinject monitors your C/C++ build to create a build specification kwmaven creates a Java build specification based on the information in your maven build file kwmavenw creates a Java build specification based on the information in your maven wrapper file kwjsspec creates a Javascript build specification file kwpyspec creates a Python build specification file kwant creates a Java build specification based on the information in your ant build file kwvcprojparser provides an alternative when kwinject cannot be used to create a build specification for a Microsoft Visual Studio 2012 or 2015 C/C++ project; however, it only provides results based on the previous generation (pre-Klocwork 2018) analysis engine kwcsprojparser creates a build specification for Visual Studio C# projects and solutions create tracefile uses kwinject to create a trace file, mainly used for debugging kwgradle creates a Java build specification based on the information in your Gradle build file kwgradlew creates a Java build specification based on the information in your Gradle wrapper file

Specify the build specification output filename and, optionally, its file path. By default, the build specification is written to kwinject.out in the current working directory. The specified file path can be absolute or relative to the workspace directory.

Specify other tool options here. Separate the options with whitespace; surround any arguments with whitespace in double quotes.

Ignore any error return codes from this step and continue.

Build specification to use for analysis. Path is relative to the workspace

XML report file in which to store Klocwork results. Optional, in case you want to use the XML report for something custom; otherwise, a default file is created for the post-build step.

Additional options added to the kwciagent run command. For example, specify the number of jobs/threads to use (--jobs-num) or which filters to apply (--severity --taxonomy --system)

See the Klocwork documentation for more information.

Analyze changed files only

This feature allows for quick, incremental analyses of changed source files to enable pre/post-checkin/commit-like behavior . The goal is that only changed files are analyzed by the Klocwork kwciagent tool to replicate the local analysis developers would perform by using our supported IDE plugins or the command line utility. To enable this behavior, the plugin takes a list of the changed files from the SCM; this enables the system to analyze only the changed files when the workspace isn’t kept. Leave this cleared to analyze the whole project, or, if the workspace is kept, to perform a standard incremental analysis.

Diff file list

The diff file list is the file that contains the changed source files for Klocwork to analyze. All analyzed files must exist in the build specification generated by kwinject.

Note: All files to be analyzed must exist in the build specification.

Using Git

If using Git, provide the previous commit that Git should perform a "diff" against. The change list between the current commit and the specified previous commit will be added to the diff file list for Klocwork to process by automatically calling "git diff <previous_commit>" during the build. Note: If you are using Git jenkins plugin to obtain source files for you pipeline job be sure to use 'Pipeline script from SCM' and specify the previous commit with the environment variable, 'GIT_PREVIOUS_COMMIT'. Also be aware that the first build in the job won't be able to access GIT_PREVIOUS_COMMIT and the first build will run full CI analysis.

Manual

If you are not using Git, or want to manually generate the change list by using Git, select this option. You will need to generate the diff file list by using a custom build-step (or similar). List one changed source file on each line of the file.

Full integration analysis build failure conditions (Full)

Create multiple build failure conditions by using queries that are sent to the Klocwork Server through the Web API.

Filter issues based on the search query, then provide the status to set the build to, along with the threshold (the number of issues to meet this criteria).

Note: unless specified, the query runs with issue grouping turned off (grouping:off).

Differential analysis build failure conditions (CI)

Set a threshold for the differential analysis build failure conditions. Pass the build if the threshold is not exceeded; fail otherwise.

This step checks the XML report generated by the differential analysis build step. You can filter which issues appear in this report by providing additional options to the differential analysis build step.

This step counts the total number of issues in the XML report.

Build specification to use for analysis. Path is relative to the workspace.

Specify the location of the tables directory, for example, ${MY_VAR}/kwtables.

Ignore compile errors encountered by kwbuildproject. This setting will not ignore a return code that indicates that kwbuildproject failed to the extent that no results are generated.

Optionally, provide configuration files to import to the project before running the analysis. If the checker configuration (for example, analysis_profile.pconf) is under version control, you can provide the file here and it will be automatically imported for each build.

Specify multiple files by separating them with commas (",").

By default, kwdeploy runs before the analysis, to ensure the checkers are up-to-date. Enable this setting if you don't want kwdeploy to run before the analysis.

Optional setting to specify the name of an existing Klocwork project. Klocwork will duplicate that project's configuration settings.

Enable to create a new Klocwork project on the server if one does not exist with the name specified. This can be useful when using multi-branch pipeline jobs.

Specify the name of the build for the Klocwork server, for example, ${MY_VAR}-${GIT_COMMIT}. If empty, Klocwork uses an auto increment to name the builds.

Cross synchronisation reads and writes to the Klocwork database. Therefore, we strongly recommend that you first try a Dry Run of the command (which skips the writing) and verify that the command works as expected.

Specify the "last synchronisation" date (how far back Klocwork should go when synchronising issue citations).

Format is "DD-MM-YYYY hh:mm:ss".

For example, "03-00-0000 00:00:00" will go back 3 days in time.

A regular expression that is used to retrieve Klocwork projects that should be processed during synchronisation. If you want to process all projects, leave empty.

For example, if you prepend projects with "DEPT-" to indicate a particular department the regular expression "^DEPT-" will match all these projects

Additional options added to the kwxsync command.

See the Klocwork documentation for more information.