Looks like I am missing the updated warnings-ng plugin:
[image: Screenshot at 2022-06-08 09-28-02.png]

On Wednesday, June 8, 2022 at 4:00:48 AM UTC-7 [email protected] wrote:

> When you look at the installed plugins in your Jenkins, are there the 
> correct snapshot versions deployed?
>
> It should look like:
>
>
> The analysis-model code looks good (it should not be part of your master 
> branch, it should be be part of a new branch though).
> The warnings plugin fork has no changes yet?
>
>
> Am 08.06.2022 um 03:21 schrieb Simon Matthews <[email protected]>:
>
>
>
> On Tuesday, June 7, 2022 at 12:10:22 PM UTC-7 [email protected] wrote:
>
>> 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
>> - examples: 
>> https://github.com/jenkinsci/warnings-ng-plugin/tree/master/plugin/src/main/java/io/jenkins/plugins/analysis/warnings
>>
>
>
> I tried to follow  Workaround 2. 
>
> I created a file to register the tool in warnings-ng by creating the file: 
> warnings-ng-plugin/plugin/src/main/java/io/jenkins/plugins/analysis/warnings/<my
>  
> parser>.java 
>
> I copied another file from the same directory and modified to reference my 
> parser.  I note that almost all the other files in this directory extend 
> AnalysisModelParser, not ReportScanningTool, as the documentation example 
> does, so I copied one that extends AnalysisModelParser and modified this. 
>
> The documentation also talks about a pom.xml file, but I could not find a 
> similar example of a similar file. I am not sure if this is relevant to 
> what I am trying to do. 
>
> I  started docker in the warnings-ng-plug-devenv directory using the 
> "jenkins.sh" script and then ran "./go.sh" in this directory. It appeared 
> to finish, although there is an error right at the end:
> ...
> removed 
> 'docker/volumes/jenkins-home/plugins/warnings-ng.jpi.version_from_image'
> 'analysis-model-api-plugin/target/analysis-model-api.hpi' -> 
> 'docker/volumes/jenkins-home/plugins/analysis-model-api.jpi'
> cp: cannot stat 'code-coverage-api-plugin/target/*hpi': No such file or 
> directory
>
> I have noticed that I appear to have 2 docker containers running:
>
> simon@jenkins-u:/jenkins/warnings-ng-plugin-devenv$ docker container list
> CONTAINER ID   IMAGE                                          COMMAND     
>              CREATED        STATUS          PORTS                           
>                                                                   NAMES
> bd4d0076d1eb   warnings-ng-plugin-devenv_java11-agent         
> "/docker-entrypoint.…"   26 hours ago   Up 35 minutes   22/tcp, 
> 0.0.0.0:8001->8001/tcp, :::8001->8001/tcp                                   
>               warnings-ng-plugin-devenv-java11-agent-1
> 4e87949d4ec7   warnings-ng-plugin-devenv_jenkins-controller   "/sbin/tini 
> -- /usr/…"   26 hours ago   Up 35 minutes   0.0.0.0:8000->8000/tcp, 
> :::8000->8000/tcp, 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 50000/tcp   
> warnings-ng-plugin-devenv-jenkins-controller-1
>
> For good measure, I restarted the container with "docker-compose restart", 
> but I still don't see my parser in the list. 
>
> Any ideas what I might have missed? Or is my mistake to extend 
> AnalysisModelParser instead of ReportScanningTool?
>
> My work on the analysis-model can be found in 
> https://github.com/SimonMatthews-BP/analysis-model
>
>
>
>
>
>
>>
>>
>> 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]>:
>>>
>>>
>>> On Monday, June 6, 2022 at 2:46:19 PM UTC-7 [email protected] 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].
>>>
>>> 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].
>>
>> 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/90dd9527-575c-420c-8e33-3b64a652113en%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/90dd9527-575c-420c-8e33-3b64a652113en%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/82502707-a8c5-4bb6-8691-cc8aa50d83c5n%40googlegroups.com.

Reply via email to