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

2017-06-08 Thread Simon M
s 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 <simon.d@gmail.com

Writing a new "parser" for the warnings plugin.

2017-05-30 Thread Simon M
I am trying to understand how to write a new "parser" to work with the Warnings plugin. The "parser" cannot be written by extending the RegexpDocumentParser or RegexpLineParser because I need it to open and read a SQLite3 database. I have been able to write a basic plugin which runs an EDA

Re: Writing a new "parser" for the warnings plugin.

2017-05-31 Thread Simon M
parser > a good start might be the LintParser.java > > > On Wednesday, May 31, 2017 at 2:31:36 AM UTC+2, Simon M wrote: >> >> I am trying to understand how to write a new "parser" to work with the >> Warnings plugin. The "parser" cannot be writ

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

2017-06-07 Thread Simon M
at 12:03:37 PM UTC-7, Simon M wrote: > > 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 e

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

2017-06-08 Thread Simon M
/bluepearl > > On Wed, Jun 7, 2017 at 11:02 PM Simon M <simon.d@gmail.com > > wrote: > >> I have a properties file with the definitions: >> >> https://github.com/SimonMatthews-BP/BPWarnings/blob/master/src/main/resources/hudson/plugins/warnings/parser/Message

Re: Test failures on new plugin

2017-06-06 Thread Simon M
on project bluepearl: Compilation failure [ERROR] /home/simon/Plugins/BluePearlParser/src/main/java/hudson/plugins/bluepearl/RunBluePearlParser.java:[40,5] method does not override or implement a method from a supertype Line 40 is the @Override statement. Simon On Monday, June 5, 2017 at 5:45:

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

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

Test failures on new plugin

2017-06-05 Thread Simon M
I am in the process of writing a custom parser to work with the Warnings plugin. For now, I have taken the second route described in the documentation: "Writing a new standalone parser that will be deployed in a new plug-in". I have written the appropriate code to extend RegexpLineParser. I

Re: Test failures on new plugin

2017-06-06 Thread Simon M
Anyone? Any ideas? On Monday, June 5, 2017 at 5:45:51 PM UTC-7, Simon M wrote: > > I am in the process of writing a custom parser to work with the Warnings > plugin. > > For now, I have taken the second route described in the documentation: > "Writing