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

Build failed emails not going to all users who have commited

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • mailer-plugin
    • None
    • Platform: All, OS: All

      Currently hudson will only send email to the last user that has commited a
      change in source control (we are using subversion) since the last build. When a
      build breaks, all users who have commited changes since the last build should
      receive the email alerts. This should probably also apply to other alert
      mechanisms.

      Alton

          [JENKINS-1020] Build failed emails not going to all users who have commited

          uwodi created issue -

          Jesse Glick added a comment -

          This was supposed to have been fixed a few months ago - issue #747. Not working
          for you, or do you just have an old version of Hudson?

          Jesse Glick added a comment - This was supposed to have been fixed a few months ago - issue #747. Not working for you, or do you just have an old version of Hudson?

          uwodi added a comment -

          System info:
          Linux - Ubuntu 7.4
          Tomcat 5.5.23
          java 1.5.0_12

          uwodi added a comment - System info: Linux - Ubuntu 7.4 Tomcat 5.5.23 java 1.5.0_12

          Kohsuke Kawaguchi added a comment -

          Please provide Hudson version number.

          Also, there has been some report that Hudson only detects one change even when
          there are many changes that went into a build. Is this happening to you? —
          IOW, does the "changelog" page in Hudson report all your changes properly?

          Kohsuke Kawaguchi added a comment - Please provide Hudson version number. Also, there has been some report that Hudson only detects one change even when there are many changes that went into a build. Is this happening to you? — IOW, does the "changelog" page in Hudson report all your changes properly?
          Kohsuke Kawaguchi made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          uwodi added a comment -

          Yes, this issue is also occuring for me. The changelog page only reports the
          last commit. It does not report all of the commits that have occured since the
          previous build.

          uwodi added a comment - Yes, this issue is also occuring for me. The changelog page only reports the last commit. It does not report all of the commits that have occured since the previous build.

          Kohsuke Kawaguchi added a comment -

          This appears to be a duplicate of issue #856. Please re-open #856 if you still
          see this probelm after upgrading to 1.157 or later.

              • This issue has been marked as a duplicate of 856 ***

          Kohsuke Kawaguchi added a comment - This appears to be a duplicate of issue #856. Please re-open #856 if you still see this probelm after upgrading to 1.157 or later. This issue has been marked as a duplicate of 856 ***
          Kohsuke Kawaguchi made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Kohsuke Kawaguchi made changes -
          Link New: This issue duplicates JENKINS-856 [ JENKINS-856 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            uwodi uwodi
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: