URL under the section "Defining a new parser using the user interface" in this page (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin <https://www.google.com/url?q=https%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FWarnings%2BPlugin&sa=D&sntz=1&usg=AFQjCNGnl1fx1HUPkYAiH7c6mxmYD22dUw>) i not working. Can you tell me the correct URL ?
Thanks. On Monday, October 24, 2016 at 1:56:34 PM UTC+5:30, Ullrich Hafner wrote: > > Well the simplest way would be to write a parser for the warnings plug-in ( > https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin > <https://www.google.com/url?q=https%3A%2F%2Fwiki.jenkins-ci.org%2Fdisplay%2FJENKINS%2FWarnings%2BPlugin&sa=D&sntz=1&usg=AFQjCNGnl1fx1HUPkYAiH7c6mxmYD22dUw>), > > then you do not need to write a new plug-in at all. > > If this is not sufficient for you (e.g. you need to provide additional > data in the UI that will not be available in the output file of your > analysis program) you can write a new plug-in that is based on > analysis-core ( > https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins). > See the plug-ins checkstyle and findbugs to get the idea. > > Am 23.10.2016 um 23:47 schrieb Lasse Schuirmann <[email protected] > <javascript:>>: > > Hi, > > a lot of coala users have asked us to provide a Jenkins Plugin so they > can use our code analysis in Jenkins. > > I have no idea how that works exactly but I plan to do this this week > and I hope that this'll be really quick - we can already provide code > analysis results in JSON or any custom format you like as long as the > structure can be expressed with a format string. We can probably > transform that easily into something Jenkins understands. > > - It'll be licensed AGPL, like our main project. > - Contributors and proposals on how we should do this to both coala > and the plugin are very much welcome. > - We will maintain the plugin as good as possible. It's hard to keep > the plugins in sight with volunteer only developers and a whole lot of > other things going on at the project but at least we'll be able to > respond promptly to any upcoming problems. > > I'll just follow this guide: > https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial - is there > anything specific to code analysis plugins? I really hoped this would > be rather quick and painless. (E.g. building the atom plugin took us > like 15 mins.) > > Seeing forward to any hints! Cheers! > > Sincerely, > > Lasse Schuirmann > > [email protected] <javascript:> > http://coala.io/ - http://viperdev.io/ - http://gitmate.com/ > > -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/db7f0248-e9c8-4fe0-be6f-5bce4132cf08%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/db7f0248-e9c8-4fe0-be6f-5bce4132cf08%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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/4955f544-6447-4058-b423-5e0a1e632ffa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
