Slide, Thanks for the tip. I started out creating a parser this way, but I didn't like the way the warnings were reported back to the build (graphs, etc). It was likely because I didn't have the groovy script passing all the info that was needed.
I like the idea of incorporating the change into the IarParser class, that way others can benefit from it in the future. On Tue, May 14, 2013 at 11:18 AM, Slide <[email protected]> wrote: > The warnings plugin provides the ability to create new parsers via script > in the global config. This is how I've always added parsers. For internal > build tools it's nice because I don't have to maintain my own plugin for > the parsing, I can just tweak a script. > > slide > > > On Tue, May 14, 2013 at 7:40 AM, Ken O <[email protected]> wrote: > >> I'm making my first foray into Jenkins development by adding another >> parser for the warnings plugin. I've found the compiler warnings emitted >> from my version of the IAR compiler (EWARM v6.3) are not parsed properly by >> the existing IAR warnings plugin. >> >> I've created another version of the IAR plugin by copying the existing >> one and modifying the regex. Is that the correct approach? I considered >> the possibility of modifying the existing parser to handle multiple regex >> patterns but that was a little above my present level. I've been an >> embedded developer for a long time. Java dev and github is fairly new to >> me. >> >> I have the parser working - except for implementing a test case for the >> new parser. >> >> Any guidance would be helpful. >> >> Thanks to Ulli for maintaining an excellent plugin! >> >> -Ken >> >> -- >> 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]. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Website: http://earl-of-code.com > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/RWCbH1DEe34/unsubscribe?hl=en > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
