On Friday, March 11, 2016 at 10:00:29 AM UTC+3, Tomas Bjerre wrote:
>
> 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 Jenki
That what i implemented 1 year ago in
https://github.com/jenkinsci/github-integration-plugin via email-ext
templating. Templating described in email-ext plugin.
On Saturday, March 5, 2016 at 12:52:16 PM UTC+3, Tomas Bjerre wrote:
>
> Plugin Name: Violation Comments To GitHub
> My GitHub username
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-l
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
On 05.03.2016, at 10:52, Tomas Bjerre 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 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 a
