Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-08 Thread Simon M
Thanks for the suggestion. I made the changes (see repository https://github.com/SimonMatthews-BP/BPWarnings), but I still get the same error. The repository version uses src/main/java/hudson/plugins/warnings/parser/RunBluePearlParser.java and

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-08 Thread Slide
That's not matching the package layout of your code: The resources for your class need to be in the same package layout, since you have your code in: src/main/java/hudson/plugins/bluepearl Your resource would need to be in src/main/resources/hudson/plugins/bluepearl On Wed, Jun 7, 2017 at

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-08 Thread Simon M
I have a properties file with the definitions: https://github.com/SimonMatthews-BP/BPWarnings/blob/master/src/main/resources/hudson/plugins/warnings/parser/Messages.properties Simon On Wednesday, June 7, 2017 at 10:51:10 PM UTC-7, slide wrote: > > They are defined by creating a properties file

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Slide
They are defined by creating a properties file with the messages. See https://github.com/jenkinsci/warnings-plugin/blob/c5db29ed729c201e37e553521f4daf099ff36a52/src/main/resources/hudson/plugins/warnings/parser/Messages.properties#L87 for examples. On Wed, Jun 7, 2017 at 5:22 PM Simon M

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Simon M
Anyone? As far as I can see the method Messages._Warnings_runbluepearl_ParserName() isn't defined, but looking at other extensions, (for example GccParser), this and similar methods don't appear to be explicitly defined. So, how to define them implicitly? Simon On Wednesday, June 7, 2017

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Simon Matthews
I really appreciate the help you have given me. However, my plugin extension is still not working. I updated my git repository: https://github.com/SimonMatthews-BP/BPWarnings The Jenkins log shows the following error: Jun 07, 2017 6:54:02 PM

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Simon M
On Wednesday, June 7, 2017 at 6:13:15 AM UTC-7, slide wrote: > > It should show up after installing your plugin and restarting Jenkins. I > checked the source and it looked like you added the @Extension to your > parser, so it should get pulled in once the plugin is installed. What do > you

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Slide
By the way, you shouldn't need this at all https://github.com/SimonMatthews-BP/BPWarnings/blob/master/src/main/java/hudson/plugins/bluepearl/RunBluePearlParser.java#L41 The ID is one of the parameters you are passing to super in your constructor. On Wed, Jun 7, 2017 at 6:12 AM Slide

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Slide
It should show up after installing your plugin and restarting Jenkins. I checked the source and it looked like you added the @Extension to your parser, so it should get pulled in once the plugin is installed. What do you mean by #2? Are you asking how to use the warnings plugin in general? On

Warnings plugin extension: how to make it show up and to define input log file

2017-06-06 Thread Simon M
So, after getting my own log parser written and built, my next questions are: 1. How to get it to show up when adding a new parser? What needs to be defined for this? 2. How the input file to the parser is defined. I would very much appreciate any advice on these topics. My present current