Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Plugin Information

View FxCop Runner on the plugin site for more information.

FxCopCmd.exe execute plugin.


FxCopCmd.exe execute plugin.
Output xml can be used to Violations Plugin.


System configuration

  1. Open the system configuration page "Manage Jenkins->Configure system"
  2. Enter the path to the FxCop command line client, that should be used by Jenkins.
  • Example: C:\Program Files (x86)\Microsoft Fxcop 10.0\FxCopCmd.exe

Job configuration



FxCop Name

Select FxCop.

Assembly Files

Assembly file(s) to analyze.
You can specify multiple analyze assemblies by separating them with new-line or space.

Output XML

FxCop project or XML report output file.

RuleSet File

Rule set to be used for the analysis.


Suppress analysis results against generated code.


Write output XML and project files even in the case where no violations occurred.

Command Line Arguments

This is a whitespace separated list of command line arguments you can specify.

Fail build on test failure

Fail build on test failure


Version 1.1 (02/28/2013)
  • add forceOutput field.
Version 1.0 (02/26/2013)
  • Initial release
  • No labels