Jenkins' Warnings Next Generation Plugin supports the following report formats. If your tool is supported, but has no custom icon yet, please file a pull request for the Warnings Next Generation Plugin.
If your tool is not yet supported you can
- define a new Groovy based parser in the user interface
- export the issues of your tool to the native XML format (or any other format)
- provide a parser within a new small plugin.
If the parser is useful for other teams as well please share it and provide pull requests for the Warnings Next Generation Plug-in and the Analysis Parsers Library.
| ID | Pipeline Symbol | Icon | Name | Default Pattern |
|---|---|---|---|---|
| acu-cobol | acuCobol() |
|
AcuCobol | - |
| gnat | gnat() |
|
Ada Compiler (gnat) | - |
| android-lint | androidLintParser() |
|
Android Lint | - |
| 💡 Use the flag -p. | ||||
| ansiblelint | ansibleLint() |
|
Ansible Lint | - |
| 💡 Use the flag -p. | ||||
| scannercli | aquaScanner() |
|
Aqua Scanner | - |
💡 Use commandline scannercli scan 'image' --jsonfile results.json, see Aqua Scanner CLI for usage details.
|
||||
| trivy | trivy() |
|
Aquasec Trivy | - |
💡 Use commandline trivy image -f json -o results.json 'image', see tivy on Github for usage details.
|
||||
| armcc | armCc() |
|
Armcc Compiler | - |
| aspectj | ajc() |
|
AspectJ | - |
| axivion-suite | axivionSuite() |
|
Axivion Suite | - |
| 💡 For using Axivion Suite, set up your analysis project and the web service. Provide the URL and credentials. | ||||
| bluepearl | bluepearl() |
|
Blue Pearl Visual Verification Suite | - |
| brakeman | brakeman() |
|
Brakeman | **/brakeman-output.json |
💡 Reads Brakeman JSON reports. Use commandline brakeman -o brakeman-output.json output.See Brakeman documentation for usage details. |
||||
| buckminster | buckminster() |
|
Buckminster | - |
| cadence | cadence() |
|
Cadence Incisive | - |
| cargo | cargo() |
|
Cargo Check | - |
💡 Use commandline cargo check --message-format json
|
||||
| ccm | ccm() |
|
CCM | - |
| checkstyle | checkStyle() |
|
CheckStyle | **/checkstyle-result.xml |
| clair | clair() |
|
Clair Scanner | - |
💡 Reads Clair json data. Use commandline clair-scanner --report="/target/clair.json" output.See clair-scanner on Github for usage details. |
||||
| clang | clang() |
|
Clang | - |
| clang-analyzer | clangAnalyzer() |
|
Clang Analyzer | - |
| 💡 Use options --analyze --analyzer-output plist-multi-file | ||||
| clang-tidy | clangTidy() |
|
Clang-Tidy | - |
| cmake | cmake() |
|
CMake | - |
| code-analysis | codeAnalysis() |
|
Code Analysis | - |
| code-generator | codeGeneratorParser() |
|
Code Generator Tool | - |
| code-checker | codeChecker() |
|
CodeChecker | - |
| codenarc | codeNarc() |
|
CodeNarc | - |
| coolflux | coolflux() |
|
Coolflux DSP Compiler | - |
| cpd | cpd() |
|
CPD | **/cpd.xml |
| cppcheck | cppCheck() |
|
CPPCheck | - |
| 💡 Use options --xml --xml-version=2 | ||||
| cpplint | cppLint() |
|
Cpplint | - |
💡 You need to use the Eclipse format with the option --output=eclipse
|
||||
| crosscore-embedded-studio | CrossCoreEmbeddedStudioParser() |
|
CrossCore Embedded Studio (CCES) | - |
| csslint | cssLint() |
|
CSS-Lint | - |
| dart | dart() |
|
Dart Analyze | - |
| detekt | detekt() |
|
Detekt | - |
| 💡 Use option --output-format xml. | ||||
| docfx | docFx() |
|
DocFX | - |
| dockerlint | dockerLint() |
|
Dockerfile Lint | - |
💡 Use commandline dockerfile_lint -j output.See dockerfile_lint on Github for usage details. |
||||
| doxygen | doxygen() |
|
Doxygen | - |
💡 Execute doxygen:As shell command ( cat Doxyfile; echo WARN_FORMAT='$file:$line: $text' ) | doxygen -As batch command ( type Doxyfile & echo WARN_FORMAT='$file:$line: $text' ) | doxygen -
|
||||
| dr-memory | drMemory() |
|
Dr. Memory | - |
| dscanner | dscanner() |
|
DScanner | **/dscanner-report.json |
| eclipse | eclipse() |
|
Eclipse ECJ | - |
|
💡 Create an output file that contains Eclipse ECJ output, in either XML or text format. To log in XML format, specify ".xml" as the file extension to the -log argument:
To log in text format, specify any file extension except ".xml" to the -log argument:
|
||||
| embedded-engineer | embeddedEngineerParser() |
|
Embedded Engineer Tool | - |
| erlc | erlc() |
|
Erlang Compiler (erlc) | - |
| error-prone | errorProne() |
|
Error Prone | - |
| eslint | esLint() |
|
ESLint | - |
| 💡 Use option --format checkstyle. | ||||
| findbugs | findBugs() |
|
FindBugs | **/findbugsXml.xml |
| flake8 | flake8() |
|
Flake8 | - |
|
💡 Run flake8 as |
||||
| flawfinder | flawfinder() |
|
FlawFinder | - |
💡 Use commandline flawfinder -S.
|
||||
| flex | flexSdk() |
|
Flex SDK Compiler | - |
| fxcop | fxcop() |
|
FxCop | - |
| gendarme | gendarme() |
|
Gendarme | - |
| ghs-multi | ghsMulti() |
|
GHS Multi Compiler | - |
| gcc | gcc() |
|
GNU C Compiler (gcc) | - |
| gcc3 | gcc3() |
|
GNU C Compiler 3 (gcc) | - |
| fortran | gnuFortran() |
|
GNU Fortran Compiler | - |
| golint | goLint() |
|
Go Lint | - |
| go-vet | goVet() |
|
Go Vet | - |
| groovy | groovyScript() |
|
Groovy Parser | - |
| grype | grype() |
|
Grype | **/grype-report.json |
| hadolint | hadoLint() |
|
HadoLint | - |
💡 Use commandline hadolint --format json Dockerfile output.See hadolint on Github for usage details. |
||||
| iar-cstat | iarCstat() |
|
IAR C-STAT | - |
|
💡 The IAR C-STAT static analysis tool finds potential issues in code by doing an analysis on the source code level. Use the following icstat command to generate the output on stdout in the correct format: |
||||
| iar | iar() |
|
IAR Compiler (C/C++) | - |
| 💡 The IAR compilers need to be started with option --no_wrap_diagnostics. Then the IAR compilers will create single-line warnings. | ||||
| iblinter | ibLinter() |
|
IbLinter | - |
| 💡 Use configuration reporter: \”checkstyle\”. | ||||
| xlc | xlc() |
|
IBM XLC Compiler | - |
| infer | infer() |
|
Infer | - |
| 💡 Use option --pmd-xml. | ||||
| intel | intel() |
|
Intel Compiler (C, Fortran) | - |
| idea | ideaInspection() |
|
IntelliJ IDEA Inspections | - |
| java | java() |
|
Java Compiler | - |
| javadoc-warnings | javaDoc() |
|
JavaDoc | - |
| jc-report | jcReport() |
|
JCReport | - |
| js-hint | jsHint() |
|
JsHint | - |
| jslint | jsLint() |
|
JSLint | - |
| junit | junitParser() |
|
JUnit | - |
| klocwork | klocWork() |
|
Klocwork | - |
| kotlin | kotlin() |
|
Kotlin | - |
| ktlint | ktLint() |
|
KtLint | - |
| 💡 Use option --reporter=checkstyle. | ||||
| maven-warnings | mavenConsole() |
|
Maven | - |
| taglist | tagList() |
|
Maven Taglist Plugin | **/taglist.xml |
| modelsim | modelsim() |
|
Mentor Graphics Modelsim/Questa Simulators | - |
| metrowerks | metrowerksCodeWarrior() |
|
Metrowerks CodeWarrior Compiler | - |
|
💡 Ensure that the output from the CodeWarrior build tools is in the expected format. If there are warnings present, but they are not found, then it is likely that the format is incorrect. The mwccarm compiler and mwldarm linker tools may support a configurable message style. This can be used to enforce the expected output format, which may be different from Metrowerks CodeWarrior (and thus require a different tool). For example the following could be appended to the build flags:
|
||||
| msbuild | msBuild() |
|
MSBuild | - |
| mypy | myPy() |
|
MyPy | - |
| nag-fortran | nagFortran() |
|
NAG Fortran Compiler | - |
| issues | issues() |
|
Native Analysis Model Format | - |
|
💡 Create an output file that contains issues in the native Warnings Plugin format, in either XML or JSON. The supported format is identical to the format of the remote API calls. The parser is even capable of reading individual lines of a log file that contains issues in JSON format. |
||||
| oelint-adv | oelintAdv() |
|
oelint-adv | - |
| open-tasks | taskScanner() |
|
Open Tasks Scanner | - |
| invalids | invalids() |
|
Oracle Invalids | - |
| ot-docker-linter | otDockerLint() |
|
OT Docker Linter | - |
💡 Use commandline ot-docker-linter audit --docker.file Dockerfile -o json output.See ot-docker-linter on Github for usage details. |
||||
| owasp-dependency-check | owaspDependencyCheck() |
|
OWASP Dependency Check | **/dependency-check-report.json |
| pclint | pcLint() |
|
PC-Lint Tool | - |
|
💡 Use the following PC-Lint properties to create an output file in the correct format: |
||||
| pep8 | pep8() |
|
PEP8 | - |
| perforce | perforce() |
|
Perforce Compiler | - |
| perl-critic | perlCritic() |
|
Perl::Critic | - |
| php | php() |
|
PHP Runtime | - |
| php-code-sniffer | phpCodeSniffer() |
|
PHP_CodeSniffer | - |
| 💡 Use option --report=checkstyle. | ||||
| phpstan | phpStan() |
|
PHPStan | - |
| 💡 Use the options: --no-progress --error-format=checkstyle | ||||
| pit | pit() |
|
PIT | **/mutations.xml |
| pmd | pmdParser() |
|
PMD | **/pmd.xml |
| polyspace-parser | polyspaceParser() |
|
Polyspace Tool | - |
|
💡 Reads reports of Polyspace Static Analysis Tool by MathWorks. Used for BugFinder and CodeProver result files. Report can be generated with command: polyspace-results-export -format csv -results-dir -output-name -key |
||||
| prefast | prefast() |
|
PREfast | - |
| protolint | protoLint() |
|
ProtoLint | - |
| puppetlint | puppetLint() |
|
Puppet Lint | - |
💡 You will need a recent enough version that supports --log-format flag. When running puppet-lint, make sure you use the log format %{path}:%{line}:%{check}:%{KIND}:%{message}. Complete example: find. -iname *.pp -exec puppet-lint --log-format "%{path}:%{line}:%{check}:%{KIND}:%{message}" {} \;
|
||||
| pvs-studio | PVSStudio() |
|
PVS-Studio | **/*.plog |
| pydocstyle | pyDocStyle() |
|
PyDocStyle | - |
| pylint | pyLint() |
|
Pylint | - |
|
💡 Start Pylint using this custom message template (can also be configured via a pylintrc configuration file):
|
||||
| qac | qacSourceCodeAnalyser() |
|
QA-C Sourcecode Analyser | - |
| qt-translation | qtTranslation() |
|
Qt translations | - |
| 💡 Reads translation files of Qt, which are created by "lupdate" or "Linguist". | ||||
| analysis-model | analysisParser() |
|
Registered Parser | - |
| dupfinder | dupFinder() |
|
Resharper DupFinder | - |
| resharper | resharperInspectCode() |
|
Resharper Inspections | - |
| revapi | revApi() |
|
Revapi | **/target/revapi-result.json |
| robocopy | robocopy() |
|
Robocopy | - |
| rflint | rfLint() |
|
Robot Framework Lint | - |
| rubocop | ruboCop() |
|
Rubocop | - |
💡 Use commandline rubocop --format progress.
|
||||
| sarif | sarif() |
|
SARIF | - |
| scala | scala() |
|
Scala Compiler | - |
| simian | simian() |
|
Simian | - |
| simulink-check-parser | simulinkCheckParser() |
|
Simulink Check Tool | - |
💡 Reads and Parses HTML reports of Simulink Check Tool by MathWorks. Report can be generated with command: ModelAdvisor.summaryReport(ModelAdvisor.run(, , , ))
|
||||
| sonar | sonarQube() |
|
SonarQube Issues | **/sonar-report.json |
| sphinx | sphinxBuild() |
|
Sphinx Build | - |
| spotbugs | spotBugs() |
|
SpotBugs | **/spotbugsXml.xml |
| stylecop | styleCop() |
|
StyleCop | - |
| stylelint | styleLint() |
|
Stylelint | - |
|
💡 Requires stylelint-checkstyle-reporter. Use --custom-formatter node_modules/stylelint-checkstyle-reporter/index.js -o stylelint-warnings.xml
|
||||
| sunc | sunC() |
|
SUN C++ Compiler | - |
| swiftlint | swiftLint() |
|
SwiftLint | - |
| 💡 Use configuration reporter: \”checkstyle\”. | ||||
| tasking-vx | taskingVx() |
|
TASKING VX Compiler | - |
| code-composer | tiCss() |
|
Texas Instruments Code Composer Studio | - |
| tnsdl | tnsdl() |
|
TNSDL Translator | - |
| tslint | tsLint() |
|
TSLint | - |
| 💡 Use option --format checkstyle. | ||||
| veracode-pipeline-scanner | veracodePipelineScanner() |
|
Veracode Pipeline Scanner | - |
💡 Use commandline java -jar pipeline-scan.jar --json_output=true --json_output_file=results.json, see Veracode Pipeline Scanner for usage details.
|
||||
| diabc | diabC() |
|
Wind River Diab Compiler (C/C++) | - |
| xmllint | xmlLint() |
|
XML-Lint | - |
| yamllint | yamlLint() |
|
YamlLint | - |
| 💡 Use option -f parsable. | ||||
| yui | yuiCompressor() |
|
YUI Compressor | - |
| zptlint | zptLint() |
|
ZPT-Lint | - |