[
https://issues.jenkins-ci.org/browse/JENKINS-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160174#comment-160174
]
Ulli Hafner commented on JENKINS-6748:
--------------------------------------
If I remember correctly two volunteers wanted to dig into that issue but since
I didn't hear anything I think there is no progress (there are also some GitHub
comments or issues about that problem).
Martin, I'm not sure if I misunderstand your use case but it looks much simpler
that the original request and is already solved: if you set the new warning
count to 0, then all committers participating in that build will become an
email on any new warning. This is quite similar to the build failed email due
to compile errors: Here you also don't know which commit actually broke the
build, all committers get that Email.
> 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
