Parsing report files produced by static code analysis is something that is valuable also outside Jenkins community. That is why I think it should be implemented in a library and released to Maven Central, not only Jenkins Maven repos. And so I have done ( https://github.com/tomasbjerre/violations-lib). I have the same argument for commenting (https://github.com/tomasbjerre/violation-comments-lib) and commenting GitHub ( https://github.com/tomasbjerre/violation-comments-to-github-lib).
This enables me to easily create Gradle and Maven plugins for this. Which means I can also do this in Travis or any other build server. My plugin is basically just a configuration GUI and that is something that I think other developers should also aim for. Simple and less complex. But I will have a closer look at you links! See if there is something I can use. 2016-03-10 21:19 GMT+01:00 James Nord <[email protected]>: > There is already one api (which is used by gerrit) to contribute messages > - and there is an implementation that picks up findbugs/checkstyle from the > existing plugins. > > It would be great if these could all be aligned so there was one message > contributing api - then all you need is a single thing to bridge the report > plugin to this API and then you can have whatever publisher implementation > you want and you all build of the same work rather than having lots of > differences. > > > https://github.com/jenkinsci/gerrit-trigger-plugin/blob/master/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/GerritMessageProvider.java#L112-L124 > https://github.com/jyrkiput/gerrit-static-analysis-comments > > This also allows having general top level messages - such that there is > integration with the Build Failure Analyzer plugin - and > https://github.com/switchgears/gerrit-review-buddy/blob/master/src/main/java/org/jenkinsci/plugins/gerritreviewbuddy/MessageProvider.java > > > /James > > On Saturday, March 5, 2016 at 7:34:06 PM UTC, Daniel Beck wrote: >> >> >> On 05.03.2016, at 10:52, Tomas Bjerre <[email protected]> wrote: >> >> > Plugin Name: Violation Comments To GitHub >> > My GitHub username: tomasbjerre >> > Existing repo: >> https://github.com/tomasbjerre/violation-comments-to-github-jenkins-plugin >> > Doc: >> https://github.com/tomasbjerre/violation-comments-to-github-jenkins-plugin >> > >> > This plugin will find report files from static code analysis and >> comment GitHub pull requests with the content. Here is a live demo of what >> it may look like on GitHub. >> >> Hi Thomas, >> >> We changed our process to ensure no hosting requests get lost. Please >> follow the instructions on: >> >> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Requesthosting >> >> Daniel > > -- > 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/h_RbZhsZwBQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/6596c3d0-e077-4469-baf4-584520ea8ed1%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/6596c3d0-e077-4469-baf4-584520ea8ed1%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/CAK89W5K34ebp%2Bu6SFu0ZzKiaw16nZiZniDrRdAuCpsj%2B5sN%2B9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
