-
Improvement
-
Resolution: Duplicate
-
Minor
-
None
Not entirely clear to me how to use recordIssues when using a Custom Parser based on my reading of the Warnings documentation here:
https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md
Presumably I'm simply misunderstanding how to use the Custom Parser in a pipeline, and nothing is actually broken. However, I'm reasonably sure that there are likely others like me who are failing or who would fail, to understand the right way to do this.
Jenkinsfile:
stage('Static Analysis') { steps { sh 'luacheck -d --no-max-line-length --no-global --formatter TAP ./bsmtpd/modules/*.lua > ./static_analysis_junit.xml || true' recordIssues tools: [[pattern: 'static_analysis_junit.xml', tool: [$class: 'luacheck']]] } }
Jenkins -> configuration -> Groovy Based Warnings Parsers: <– (This location should possibly be made more explicit in documentation.)
I've run the Jenkinsfile with a whole mess of different possible configuration for the recordIssues line, and been unable to find anything that works. Most return simply:
Cheers