Skip to content

[JENKINS-747] List of possible culprits for repeated failed builds should be cumulative #416

Description

@jenkins-infra-bot

Currently when a build fails, Hudson just sends mail (if so configured) to those
who committed changes to the build. In fact it ought to send mail to everyone
who committed to any immediately preceding failed builds, i.e. accumulate
recipients until the breakage is fixed. This is because the usual case is that a
commit in the first broken build has not been fixed several builds later;
occasionally someone else introduces an unrelated problem. Continuing to notify
the original culprit keeps pressure on them, and helps other committers to see
that they are not necessarily at fault.


Originally reported by jglick, imported from: List of possible culprits for repeated failed builds should be cumulative
  • status: Closed
  • priority: Major
  • component(s): mailer-plugin
  • resolution: Fixed
  • resolved: 2007-09-10T09:15:23+00:00
  • votes: 0
  • watchers: 0
  • imported: 20251211-223321
Raw content of original issue

Currently when a build fails, Hudson just sends mail (if so configured) to those who committed changes to the build. In fact it ought to send mail to everyone who committed to any immediately preceding failed builds, i.e. accumulate recipients until the breakage is fixed. This is because the usual case is that a commit in the first broken build has not been fixed several builds later; occasionally someone else introduces an unrelated problem. Continuing to notify the original culprit keeps pressure on them, and helps other committers to see that they are not necessarily at fault.

  • environment: Platform: All, OS: All
1 attachment

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions