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

Incorrectly Using Committer User Full Name in resolving Committer Email Address

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin, (1)
      repo-plugin
    • None
    • RHEL 5.8

      I have seen where this same issue has been resolved for other SCM plugins, but this is still happening when using the Repo and GIT plugins

      When using the Email Ext plugin and selecting the "Send To Committers" option on failure, it appears that the committer user's full name is being used and is creating two email addresses to be sent notification.

      For example if the committer user's full name is John Doe and the default email suffix is "@jenkins.com" then the committer designated emails are incorrectly being sent to:

      John@jenkins.com
      Doe@jenkins.com

      The committer's actual email address is not even being accessed

      Jenkins 1.472
      Email-ext 2.22
      Repo 1.2.1
      Git 1.1.21

          [JENKINS-14539] Incorrectly Using Committer User Full Name in resolving Committer Email Address

          Alex Earl added a comment -

          The email-ext plugin uses email address resolution from Jenkins core, which in turn uses all the classes that inherit from MailAddressResolver. This is not an issue with email-ext.

          Alex Earl added a comment - The email-ext plugin uses email address resolution from Jenkins core, which in turn uses all the classes that inherit from MailAddressResolver. This is not an issue with email-ext.

          Alex Earl added a comment -

          MailAddressResolver implementation for plugins you have loaded is not resolving the email address correctly. Not an issue with email-ext.

          Alex Earl added a comment - MailAddressResolver implementation for plugins you have loaded is not resolving the email address correctly. Not an issue with email-ext.

          rejesi added a comment -

          I don't quite understand what you mean by "MailAddressResolver implementation for plugins". May I ask from whom I am to get resolution
          for this issue?

          I have noted the plugins in use and believe it is from the Git plugin since you indicate it is not an email-ext issue. But as I am new to Jenkins I do not understand how to present this issue to any of the other plugin owners.

          I don't even know how it went to email-ext as opposed to Git or Jenkins or all. I would truly appreciate any help or direction in this matter as I don't want it closed until it is fixed.

          Thanks much

          rejesi added a comment - I don't quite understand what you mean by "MailAddressResolver implementation for plugins". May I ask from whom I am to get resolution for this issue? I have noted the plugins in use and believe it is from the Git plugin since you indicate it is not an email-ext issue. But as I am new to Jenkins I do not understand how to present this issue to any of the other plugin owners. I don't even know how it went to email-ext as opposed to Git or Jenkins or all. I would truly appreciate any help or direction in this matter as I don't want it closed until it is fixed. Thanks much

          Alex Earl added a comment -

          When a username only is sent to email-ext, it calls into something provided by the core to resolve that username to an email address. Plugins can implement their own address resolver. It sounds like the git plugin is what is resolving the address.

          Alex Earl added a comment - When a username only is sent to email-ext, it calls into something provided by the core to resolve that username to an email address. Plugins can implement their own address resolver. It sounds like the git plugin is what is resolving the address.

          rejesi added a comment -

          Is there anyway to move this issue over to the git plugin people or do I have to recreate another one.

          Please excuse my ignorance in this process, I still don't understand how this went to the email-ext plugin issue queue and nowhere else.

          rejesi added a comment - Is there anyway to move this issue over to the git plugin people or do I have to recreate another one. Please excuse my ignorance in this process, I still don't understand how this went to the email-ext plugin issue queue and nowhere else.

          Alex Earl added a comment -

          You put email-ext as one of the components. You just need to change the components that the issue deals with. There is an auto-complete box for the components, so find the one that matches that plugin you are using for git.

          Alex Earl added a comment - You put email-ext as one of the components. You just need to change the components that the issue deals with. There is an auto-complete box for the components, so find the one that matches that plugin you are using for git.

          rejesi added a comment -

          Changing the component to Git for possible resolution as the issue is not with email-ext

          rejesi added a comment - Changing the component to Git for possible resolution as the issue is not with email-ext

          I can confirm this problem with
          Jenkins 1.489
          GIT Plugin 1.1.26

          Michael Haslgrübler added a comment - I can confirm this problem with Jenkins 1.489 GIT Plugin 1.1.26

          Alex Earl added a comment -

          Try setting the "Create new accounts base on author/committer's email" option in the global config.

          Alex Earl added a comment - Try setting the "Create new accounts base on author/committer's email" option in the global config.

            Unassigned Unassigned
            rejesi rejesi
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: