Ulli,
I agree it would be best if they could be merged into the same parser. I'm
just not that good with regex to figure how to merge the two. The
differences are the 1) the use of quotes around the filename, 2) comma
between filename and line number, and 3) colon between linenumber and
warning
Thanks for the info Baptiste. It will come in handy when I get to the
point when I need to commit my work. I still have some design issues to
sort out first.
On Tue, May 14, 2013 at 11:40 AM, Baptiste Mathus bmat...@gmail.com wrote:
Hi,
You're on the right track :).
Here's the typical
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
Hi Ken,
I changed the regexp to:
https://github.com/jenkinsci/warnings-plugin/commit/076da03e4afbcf0ace433f6420c7f417c94049fd
Now the parser handles both formats. Will be part of the next warnings release…
Thanks, Ulli
Am 15.05.2013 um 15:53 schrieb Ken Overly ken.ove...@gmail.com:
Ulli,
Hi Ulli,
Wow! Thanks for doing that. I anticipated doing it myself and forcing me
to learn something in the process.
Thanks again.
-Ken
On Wed, May 15, 2013 at 12:28 PM, Ulli Hafner ullrich.haf...@gmail.comwrote:
Hi Ken,
I changed the regexp to:
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
Hi,
You're on the right track :).
Here's the typical way/steps to proceed:
* find or create the corresponding issue in JIRA for reference
* fork the plugin in your github account (if not already done)
* clone it locally (if not done)
* create a dedicated branch
* Create a commit in that branch
How large are the differences between the two warning formats? If they are
small I would prefer having just a single parser. This make things easer for
the user, because there is just one selection possible for IAR. Maybe we can
combine the 2 expressions into one that matches both.
Otherwise
