When I re-ran and looked at the transcript a little deeper, I think that 
the parser I built is not testing properly, so maybe there is an issue with 
it. I'll have to investigate further. There is an error flagged, but it had 
scrolled off the screen and, at the end, I got the message that the build 
had completed. I'll go back to the start to see if I can figure it out. 
It's odd, because, in my stand-alone analysis-model directory, the tests 
ran clean with my new parser. 

Simon
On Friday, June 3, 2022 at 11:35:36 AM UTC-7 Simon Matthews wrote:

> On Friday, June 3, 2022 at 1:15:35 AM UTC-7 [email protected] wrote:
>
>>
>> Looking at the first and second second go.sh, neither appear to actually 
>> copy any files from the file "analysis-model-api.jar" (or any 
>> "analysis-model-*SNAPSHOT.jar" file)  to the JENKINS_HOME directory. 
>>
>>
>> The first go.sh calls mvn install that installs the jar in your local 
>> maven repository.
>>
>
> It looks like the Jenkins running under Docker is not picking up my 
> modified version of analysis-model. I don't see the parser that I added. 
>
> I assume that I have missed a step somewhere. 
>
> I have added files for the <MyParser>SoftwareDescriptor.java, I have added 
> the reference in the ParserRegistry.java, I have added the reference in 
> ParsersTest.java and an appropriate log file. 
>
> In analysis-model, I have run "./bin/go.sh" and in warnings-ng-plug, I 
> have run "./bin/go.sh", then in the warnings-ng-plugin-devenv directory, I 
> have re-started "./jenkins.sh". 
>
> If I configure a job, I can add "Record compiler warnings and static 
> analysis results" as a post-build step, but my new parser is not in the 
> list. What could I have missed?
>
> 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/bbfeb4db-76df-4e17-8d37-08589d9c7cdcn%40googlegroups.com.

Reply via email to