My apologies if this has been fixed in a later version of the plugin or perhaps Jenkins. We're still using Hudson, but we hope to move to Jenkins and if this is still a bug are hoping to see it fixed in Jenkins (We've just not yet been able to make that transition). We're also using the Perforce plugin.

We've found two scenarios that seem to prevent the process that tries to generate the culprits email list from working correctly: when there are duplicate committers in a build, or when there are no committers in a build.

For example:

Ex. 1 - This is a build that hasn't been successful since #1648. In this case, Fred will get tagged as a culprit and receive an email, but George will not receive the email even though he is also a culprit. The presence of a build with no submitters appears to be the pattern that causes the problem. This is a very common pattern we have since we often have builds that trigger others simply so that downstream builds can build with new versions of the parent.

Changes for Build #1650
[Fred] Blah, blah

Changes for Build #1649

Changes for Build #1648
[George] Blah, blah

Ex. 2 - Here the build has not been successful since #1549. Don, Juan, and Harry get tagged as culprits and receive an email, but Boris is a culprit but is left off the list and does not receive the email. The problem appears to occur whenever there are two checkins by the same submitter for a given build. No culprits from earlier builds will be found and included in the culprit list. This is also a very common scenario for us.

Changes for Build #1550
[Don] Blah, bibby, blah.
[Juan] Blah
[Juan] Blah, foo, blah
[Harry] Bar, foo, bar

Changes for Build #1549
[Boris] Blah, blah, blah

We only email when there's unstable or failed builds. The effect this is having on our production is that developers are not receiving actionable emails, or they receive the email, but are dropped from subseuent failure and unstable messages, believing that problem has been corrected. Our team cannot rely on email then to communicate status of the few builds (of many we operate) that they are working in.