[
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162893#comment-162893
]
bnovc commented on JENKINS-12972:
---------------------------------
{{git blame}} would be faster, but you would often not get correct results.
This only works if the problem you're trying to detect was caused by the last
edit to the line the problem was exposed.
I would really like to see {{git bisect}} offered as part of a normal build
with the git plugin. That way I would immediately know who broke the build
definitively. This would save significant time in triaging, as the person
responsible could be notified automatically.
> 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
