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

Git creates usernames based on 'name' not the email.

    XMLWordPrintable

Details

    Description

      I realize mapping git author/commit users back to Jenkin's users is pain, but perhaps it could be done a little better.

      Some ideas:

      • Try looking up a user's email and comparing that.
      • Using the user portion from the email (e.g. someuser@example.com becomes someuser).
      • Looking up the user's email in LDAP, if LDAP is being used.

      The last would be ideal for us.

      Ciao!

      Attachments

        Issue Links

          Activity

            I was just hit by the same issue. E-mail should be compared against e-mail field, not processed and compared against some different field. Or at least please give an option to choose the behaviour.

            babilon Bartosz Błaszkiewicz added a comment - I was just hit by the same issue. E-mail should be compared against e-mail field, not processed and compared against some different field. Or at least please give an option to choose the behaviour.

            Hopefully this bumps this thread. I am in the exact same spot as jeremfg.
            Since this ticket looks like its stuck in limbo, did anyone find any solution to this?

            motka Matjaž Matjašec added a comment - Hopefully this bumps this thread. I am in the exact same spot as jeremfg . Since this ticket looks like its stuck in limbo, did anyone find any solution to this?
            uv Uv Wild added a comment - - edited

            BUMP TOO

            we have 6 companies working on the machine.
            You wont believe what funny names show up in the commiter list of asynchPeople.

            This is ABSOLUTELY not an option for a secure environment.  

            The aysncList we see there is neither injective and can be used to identify, nor is it surjective and I can be sure that my git server will contain the entry as this is the job of the gitserver which might not keep all the user.name 's used by its users over time.

            This is REALLY WRONG!!!

            uv Uv Wild added a comment - - edited BUMP TOO we have 6 companies working on the machine. You wont believe what funny names show up in the commiter list of asynchPeople. This is ABSOLUTELY not an option for a secure environment.   The aysncList we see there is neither injective and can be used to identify, nor is it surjective and I can be sure that my git server will contain the entry as this is the job of the gitserver which might not keep all the user.name 's used by its users over time. This is REALLY WRONG!!!
            spoorcc Ben Spoor added a comment -

            🙄 facing the same issues as described above

             

             

             

            spoorcc Ben Spoor added a comment - 🙄 facing the same issues as described above      
            spoorcc Ben Spoor added a comment -

            As a workaround I've used the field "Allowed Domains" of the email-ext plugin.

            spoorcc Ben Spoor added a comment - As a workaround I've used the field "Allowed Domains" of the email-ext plugin.

            People

              Unassigned Unassigned
              docwhat Christian Höltje
              Votes:
              48 Vote for this issue
              Watchers:
              59 Start watching this issue

              Dates

                Created:
                Updated: