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

Use maven config for email notification to last VCS commiters

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      Currently, mail to last cvs commiters of a broken build are built according to a
      basic schema: aggregate the VCS id of the user to the configured mail suffix et
      voila!

      In my current organisation, emails address and VCS user id are unrelated. For
      example: holler_g would be my cvs username and guillaume.holler@XXX.YY would be
      my email adress. According to current email adress computation, Hudson would try
      to send an email to holler_g@XXX.YY.

      The section "developers" in the maven pom.xml does the match between the
      developper VCS id (developper.id) and her email address (developper.email).

      It would be nice if Hudson could use these information to get the developper
      actual adress. If not found in the list, the behavior would fall back to default.

        Attachments

          Issue Links

            Activity

            Hide
            bwflood Brad Flood added a comment -

            upvoted. I believe this is slightly different than JENKINS-1201.

            Explanation of our use case:

            We have hundreds of developers and build jobs. The current build process (based on Jenkins 1.x) has a person hand-editing emails into the Jenkins notification section as developers change.

            I would like to automate this by capturing the information in the maven POM and driving not only Jenkins build notifications but other automated notifications as well. 

            The best place seems to be project.developers.

            {name,email}

            In looking at the current code, it appears the Jenkins maven-plugin grabs the info from project.ciManagement.notifiers.configuration.  

            It doesn't seem to be a stretch for the maven-plugin to optionally grab the notifier information from the project.developer element. This would eliminate one moving part for those of us who plan to use the developer info for more than just ciManagement notification. Without this change, the info in project.developer would have to be duplicated in ciManagement.notifiers.configuration and is therefore susceptible to errors.

            Thanks to the Jenkins team - great tool! And Blue Ocean looks tremendous.
             

            Show
            bwflood Brad Flood added a comment - upvoted. I believe this is slightly different than JENKINS-1201 . Explanation of our use case: We have hundreds of developers and build jobs. The current build process (based on Jenkins 1.x) has a person hand-editing emails into the Jenkins notification section as developers change. I would like to automate this by capturing the information in the maven POM and driving not only Jenkins build notifications but other automated notifications as well.  The best place seems to be project.developers. {name,email} In looking at the current code, it appears the Jenkins maven-plugin grabs the info from project.ciManagement.notifiers.configuration.   It doesn't seem to be a stretch for the maven-plugin to optionally grab the notifier information from the project.developer element. This would eliminate one moving part for those of us who plan to use the developer info for more than just ciManagement notification. Without this change, the info in project.developer would have to be duplicated in ciManagement.notifiers.configuration and is therefore susceptible to errors. Thanks to the Jenkins team - great tool! And Blue Ocean looks tremendous.  
            Hide
            kutzi kutzi added a comment -

            Very similar to JENKINS-1201 if not the same

            Show
            kutzi kutzi added a comment - Very similar to JENKINS-1201 if not the same

              People

              • Assignee:
                Unassigned
                Reporter:
                guillaume_holler guillaume_holler
              • Votes:
                5 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: