[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

Title: Message Title Mark Waite updated

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

Title: Message Title dor avraham assigned

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

txemi M

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

txemi M edited a

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

Dan F

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

Dan F

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162893#comment-162893 ] bnovc commented on JENKINS-12972: - {{git blame}} would be faster, but you would often not

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162424#comment-162424 ] Rob van Oostrum commented on JENKINS-12972: --- Probably makes more sense to work off

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12972: -- Assignee: (was: Ulli Hafner) Unassigning since this needs some work in core first.

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12972: -- Component/s: git Add option to run 'git bisect' to find which commit added new bugs

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12972: -- Component/s: analysis-core core Add option to run 'git bisect' to find

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159834#comment-159834 ] Eyal Edri commented on JENKINS-12972: - Not sure i understand what 'extra plugin' is, but

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159832#comment-159832 ] Ulli Hafner edited comment on JENKINS-12972 at 3/5/12 10:00 AM:

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159836#comment-159836 ] Ulli Hafner commented on JENKINS-12972: --- I think the best approach would be to have a

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

Eyal Edri created JENKINS-12972: --- Summary: 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: