-
New Feature
-
Resolution: Fixed
-
Minor
-
None
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:
Warnings by User
- mjackson: 23 warnings
- jsmith: 1,634 warnings
- jdoe: 432 warning
New Warnings by User (build #30)
- jsmith: 84 warnings
- jdoe: 4 warnings
Cheers for listening.
- is blocking
-
JENKINS-46641 Git Blame kills slave (memory overload)
-
- Resolved
-
-
JENKINS-13056 Obtain reference build from SCM/Trigger
-
- Resolved
-
- is related to
-
JENKINS-24705 Display task author from SVN or other tool
-
- Resolved
-
- relates to
-
JENKINS-47269 Option to disable logging doesn't work Git Blamer
-
- Resolved
-
-
JENKINS-47268 Warnings contain no filename
-
- Resolved
-
[JENKINS-6748] Analysis of Checkstyle Warnings per User
Component/s | New: analysis-core [ 15709 ] | |
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Attachment | New: analysis-core_blame_screenshot1.png [ 24516 ] | |
Attachment | New: analysis-core_blame_screenshot2.png [ 24517 ] |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 136843 ] | New: JNJira + In-Review [ 174588 ] |
Link |
New:
This issue is blocking |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Remote Link | New: This issue links to "Page (Jenkins Wiki)" [ 17278 ] |
Remote Link | Original: This issue links to "Page (Jenkins Wiki)" [ 17278 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |