[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title Christopher Tindall closed an issue as Duplicate Created new issue: JENKINS-55496 Jenkins / JENKINS-55063 Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage. Change By: Christopher Tindall Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title
Christopher Tindall reopened an issue
stage('Static Analysis') {
steps {
sh 'find ./ -iname *.lua | xargs luacheck -d --no-max-line-length --no-global --formatter JUnit > ./static_analysis_junit.xml || true'
recordIssues tools: [
[tool: groovyScript(parserId: 'luacheck', pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]
]
/* unstableNewAll: 1 */
}
}
Looks like this may have broken again. Using the above pipeline code the following error is generated:
java.lang.UnsupportedOperationException: must specify $class with an implementation of class io.jenkins.plugins.analysis.core.model.Tool
at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:402)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:514)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:388)
at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:361)
at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:284)
Caused: java.lang.IllegalArgumentException: Could not instantiate {tools=[{tool=@groovyScript(parserId=luacheck,pattern=static_analysis_junit.xml,reportEncoding=UTF-8)}]} for IssuesRecorder(aggregatingResults?: boolean, blameDisabled?: boolean, enabledForFailure?: boolean, failedNewAll?: int, failedNewHigh?: int, failedNewLow?: int, failedNewNormal?: int, failedTotalAll?: int, failedTotalHigh?: int, failedTotalLow?: int, failedTotalNormal?: int, filters?: RegexpFilter{ExcludeCategory(pattern: String) | ExcludeFile(pattern: String) | ExcludeModule(pattern: String) | ExcludePackage(pattern: String) | ExcludeType(pattern: String) | IncludeCategory(pattern: String) | IncludeFile(pattern: String) | IncludeModule(pattern: String) | IncludePackage(pattern: String) | IncludeType(pattern: String)}[], healthy?: int, id?: String, ignoreFailedBuilds?: boolean, ignoreQualityGate?: boolean, minimumSeverity?: String, name?: String, referenceJobName?: String, sourceCodeEncoding?: String, tool?: Tool{AcuCobol(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Ajc(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AndroidLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AnsibleLint(id?: String, ...
String, name?: String, pattern?: String, reportEncoding?: String) | SwiftLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TagList(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TaskingVx(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TiCss(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Tnsdl(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TsLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Xlc(id?: String, name?: String, pattern?: String, reportEncoding?: String) | XmlLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | YamlLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | YuiCompressor(id?: String, name?: String, pattern?: String, reportEncoding?: String) | ZptLint(id?: String, name?: String, pattern?: String, reportEncoding?: String)}[], unhealthy?: int, unstableNewAll?: int, unstableNewHigh?:
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title Ulli Hafner resolved as Fixed Fixed in warnings-ng 1.0.0-beta7 and analysis-model-api-beta16. Note that the syntax of the step has been simplified. Jenkins / JENKINS-55063 Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage. Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title Christopher Tindall commented on JENKINS-55063 Re: Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage. Thank you so much! It worked great (once I realized I needed to update the warnings-ng plugin again ) I really appreciate the help, amazingly fast turnaround and the very sexy plugin too. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title
Ulli Hafner edited a comment on JENKINS-55063
Re: Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Yes, I need to add a section about the Groovy parser in the documentation.You need to use the GroovyScript tool:{code}recordIssues tools: [[ tool: groovyScript(parserId: 'luacheck',pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]]{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title Ulli Hafner commented on JENKINS-55063 Re: Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage. Yes, I need to add a section about the Groovy parser in the documentation. You need to use the GroovyScript tool: recordIssues tools: [[groovyScript(parserId: 'luacheck', pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title
Christopher Tindall updated an issue
Jenkins / JENKINS-55063
Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Change By:
Christopher Tindall
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:{code:java}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']]]}}{code} Jenkins -> configuration -> Groovy Based Warnings Parsers: <– (This location should possibly be made more explicit in documentation.)!image-2018-12-06-17-05-08-306.png! 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:!image-2018-12-06-17-08-01-006.png!Cheers
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title
Christopher Tindall created an issue
Jenkins / JENKINS-55063
Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Issue Type:
Improvement
Assignee:
Ulli Hafner
Attachments:
image-2018-12-06-17-05-08-306.png, image-2018-12-06-17-08-01-006.png
Components:
warnings-ng-plugin
Created:
2018-12-07 01:13
Priority:
Minor
Reporter:
Christopher Tindall
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 a
