title: Can Jenkins (continuous build) pinpoint the commit that caused a build failure?
body: <p>Jenkins says a build succeeded or failed, but can it identify the exact commit (and author!) that caused a build to fail?</p>
  
  <p><a href="https://issues.jenkins-ci.org/browse/JENKINS-12972" rel="noreferrer">This issue</a> would seem to indicate no.</p>
  
  <p><strong>Edit</strong>: From my exchange with Pace:</p>
  
  <blockquote>
    <p>What I see is "include culprits", which is everyone since the last
    build. I don't want that. I want THE culprit, with Jenkins doing the
    binary search. If Jenkins does two builds 10 commits apart, I don't
    want 10 possible culprits, I want it to find <strong>the one</strong>.</p>
  </blockquote>
  
  <p>I haven't yet heard how to do that.</p>