Plugin Hosting Request: Violation Comments to GitHub

53 views
Skip to first unread message

Tomas Bjerre

unread,
Mar 5, 2016, 4:52:16 AM3/5/16
to Jenkins Developers
Plugin Name: Violation Comments To GitHub
My GitHub username: tomasbjerre

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.

Daniel Beck

unread,
Mar 5, 2016, 2:34:06 PM3/5/16
to jenkin...@googlegroups.com
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

James Nord

unread,
Mar 10, 2016, 3:19:58 PM3/10/16
to Jenkins Developers, m...@beckweb.net
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.


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

Tomas Bjerre

unread,
Mar 11, 2016, 2:00:29 AM3/11/16
to jenkin...@googlegroups.com
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.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6596c3d0-e077-4469-baf4-584520ea8ed1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Kanstantsin Shautsou

unread,
Mar 12, 2016, 7:26:41 AM3/12/16
to Jenkins Developers
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.

Kanstantsin Shautsou

unread,
Mar 12, 2016, 7:30:22 AM3/12/16
to Jenkins Developers


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 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.
And that is already implemented in http://docs.sonarqube.org/display/PLUG/GitHub+Plugin  
Reply all
Reply to author
Forward
0 new messages