Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59

Send mail to users committing to a failed build

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      Like CC config <email defaultsuffix="@something.org">. If a build fails,
      everyone who committed to that build gets a notification.

          [JENKINS-59] Send mail to users committing to a failed build

          Jesse Glick added a comment -

          Adding Trung to CC.

          Jesse Glick added a comment - Adding Trung to CC.

          Quoting from the e-mail help screen:

          If configured, Hudson will send out an e-mail to the specified recipients when a
          certain important event occurs.

          1. Every failed build triggers a new e-mail.
          2. A successful build after a failed (or unstable) build triggers a new
          e-mail, indicating that a crisis is over.
          3. An unstable build after a successful build triggers a new e-mail,
          indicating that there's a regression.
          4. Unless configured, every unstable build triggers a new e-mail, indicating
          that regression is still there.

          For each kind of events, what recipients do you suggest should receive e-mails?

          At my work, we usually send the e-mail to the whole engineers, alerting the
          situation. That makes sure that people are aware of the problem, which is handy
          for example when someone does "commit and leave".

          Are you sure you want to limit the e-mails to the people who committed?

          Kohsuke Kawaguchi added a comment - Quoting from the e-mail help screen: If configured, Hudson will send out an e-mail to the specified recipients when a certain important event occurs. 1. Every failed build triggers a new e-mail. 2. A successful build after a failed (or unstable) build triggers a new e-mail, indicating that a crisis is over. 3. An unstable build after a successful build triggers a new e-mail, indicating that there's a regression. 4. Unless configured, every unstable build triggers a new e-mail, indicating that regression is still there. For each kind of events, what recipients do you suggest should receive e-mails? At my work, we usually send the e-mail to the whole engineers, alerting the situation. That makes sure that people are aware of the problem, which is handy for example when someone does "commit and leave". Are you sure you want to limit the e-mails to the people who committed?

          Jesse Glick added a comment -

          Sorry for not being clear - I was not suggesting limiting the emails. Rather,
          email on qualifying events should still be sent to all configured addresses,
          and (if configured to do so) to those users found in the changelog. This is
          how CruiseControl works (see URL for docs), and this is how our organization has
          done things in the past (using an in-house system). We have a general mail alias
          broken_builds@host which anyone can subscribe to, but even if you aren't
          subscribed to that for whatever reason, you will still be notified if you broke
          the build. Some organizations may have a mandatory policy re. build mail
          subscription so they would not use this option.

          Jesse Glick added a comment - Sorry for not being clear - I was not suggesting limiting the emails. Rather, email on qualifying events should still be sent to all configured addresses, and (if configured to do so) to those users found in the changelog. This is how CruiseControl works (see URL for docs), and this is how our organization has done things in the past (using an in-house system). We have a general mail alias broken_builds@host which anyone can subscribe to, but even if you aren't subscribed to that for whatever reason, you will still be notified if you broke the build. Some organizations may have a mandatory policy re. build mail subscription so they would not use this option.

          implemented.

          Kohsuke Kawaguchi added a comment - implemented.

          Jesse Glick added a comment -

          It works.

          Jesse Glick added a comment - It works.

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: