[
https://issues.jenkins-ci.org/browse/JENKINS-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160165#comment-160165
]
Martin Hanus commented on JENKINS-6748:
---------------------------------------
Hey all,
It's been a while since last comment :). I'm quite interested in this issue
since we would like to use similar behaviour in our build system. We would like
to compare checkstyle violations before and after commit. If it get's increased
after commit, we would like to send off emails with notification (same as when
build fails). Therefore I would like to check on this issue, if it's going to
be developed or it's dead and left behind :). Thanks.
> Analysis of Checkstyle Warnings per User
> ----------------------------------------
>
> Key: JENKINS-6748
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6748
> Project: Jenkins
> Issue Type: New Feature
> Components: analysis-core, checkstyle
> Affects Versions: current
> Reporter: ahhughes
> Assignee: Ulli Hafner
> Priority: Minor
>
> Checkstyle warnings generally arise because a developer is running an auto
> format that is not in sync with a project's standard, or they are choosing
> not to format.
> The current checkstyle analysis tend to display where warnings are, but not
> where they come from. What I would like is to see is a 'Warnings By User'
> analysis (user is the commit user).
> Then you can easily see who's IDE is out of whack, or who's being slack -
> even if that's happens to be me :)
> Example:
> h3. Warnings by User
> * mjackson: 23 warnings
> * jsmith: 1,634 warnings
> * jdoe: 432 warning
> h3. New Warnings by User (build #30)
> * jsmith: 84 warnings
> * jdoe: 4 warnings
> Cheers for listening.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
