Workaround 1: use a pipeline and not a Freestyle Job

Workaround 2: register your parser in the warnings plugin, see:
- documentation: 
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Custom-Plugin.md#register-the-tool
 
<https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Custom-Plugin.md#register-the-tool>
- examples: 
https://github.com/jenkinsci/warnings-ng-plugin/tree/master/plugin/src/main/java/io/jenkins/plugins/analysis/warnings
 
<https://github.com/jenkinsci/warnings-ng-plugin/tree/master/plugin/src/main/java/io/jenkins/plugins/analysis/warnings>



> Am 07.06.2022 um 19:54 schrieb Simon Matthews <[email protected]>:
> 
> 
> 
> On Tuesday, June 7, 2022 at 2:45:58 AM UTC-7 [email protected] wrote:
> In your Jenkinsfile of your job where you want to use the parser. Or are you 
> using a Freestyle project? 
> 
> I think in Freestyle projects I forgot to add a dynamic selection of the 
> parser ID in the UI up to now. I should file an issue for this bug. In this 
> case you need to register your parser in the warnings plugin as well...
> 
> Can you tell me how to work around this? At least to show that my parser is 
> working?
> 
> Simon 
> 
> 
>> Am 07.06.2022 um 03:03 schrieb Simon Matthews <[email protected] 
>> <applewebdata://4F4472B5-D816-4549-B9EB-891381CD90C0>>:
>> 
> 
>> 
>> On Monday, June 6, 2022 at 2:46:19 PM UTC-7 [email protected] 
>> <http://gmail.com/> wrote:
>> 
>> Thanks for your reply. 
>> 
>> To update on progress, I had not previously added the 
>> analysis-model/src/test/java/edu/hm/hafner/analysis/parser/<my new 
>> parser>ParserTest.java file. I have now added that and the unit tests are 
>> passing. 
>> 
>> The parser is not listed in the UI, because the parser is not registered in 
>> the warnings plugin yet. 
>> But you can invoke the parser already using:
>> 
>> recordIssues tool: analysisParser(pattern: 'your-report-file.xml', 
>> analysisModelId: 'your-id')
>> Does that work?
>> 
>> 
>> It's not clear to me how I run that command, or what file I add it to. 
>> 
>> Simon
>> 
>> 
>> 
> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] 
>> <applewebdata://4F4472B5-D816-4549-B9EB-891381CD90C0>.
> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/e1d2aaa9-a418-431d-80ef-2a7b26b96643n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/e1d2aaa9-a418-431d-80ef-2a7b26b96643n%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/ef235a57-19bf-48e5-b875-a9aa24106f50n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/ef235a57-19bf-48e5-b875-a9aa24106f50n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/693F946D-E2C3-407C-9B78-3B053F5EA81A%40gmail.com.

Reply via email to