Can Jenkins (continuous assembly) determine the fixation that caused the assembly to fail?

Jenkins says the assembly succeeded or failed, but can it determine the exact commit (and the author!) That caused the assembly to fail?

This problem seems to indicate a lack.

Change . From my exchange with Pace:

What I see is “turn on criminals,” that is, to build everyone since the last. I do not want it. I want a criminal, with Jenkins, a binary search. If Jenkins makes two assemblies, then 10 commits, I do not want 10 possible culprits, I want him to find one .

I have not heard how to do this.