[
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162423#comment-162423
]
Eyal Edri commented on JENKINS-12972:
-------------------------------------
So maybe 'git bisect' isn't the right approach?
findbugs knows where the bug is (which class/what line), so i assume it can
compare between the code diff from each git commit and his findbugs report and
show a "suspected commit" that introduced the breakage.
i assume this will be relevant to any other plugin (pmd,checkstyle,etc...).
> Add option to run 'git bisect' to find which commit added new bugs
> -------------------------------------------------------------------
>
> Key: JENKINS-12972
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
> Project: Jenkins
> Issue Type: New Feature
> Components: analysis-core, core, findbugs, git
> Reporter: Eyal Edri
> Priority: Minor
>
> Today, when you run find-bugs plug-in triggered by a git commit, you can't
> know exactly which commit added those bugs.
> It becomes especially difficult to know when a high volume of commits is
> pushed at once.
> find-bugs plug-in could have a new option to tick in the 'advanced section',
> which will do a 'git bisect' on the git commits that caused a new bug and
> display/email to commiter who did it.
> that would simply and automate the process of finding who wrote the bug.
--
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
