|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-13788) Git user and Crowd 2 ... [email protected] (JIRA)
- [JIRA] (JENKINS-13788) Git user and Cro... [email protected] (JIRA)
- [JIRA] (JENKINS-13788) Git user and Cro... [email protected] (JIRA)
- [JIRA] (JENKINS-13788) Git user and Cro... [email protected] (JIRA)

Regardless of whether using the Crowd plugin or not, the Git plugin (or Jenkins) create users (in Filesystem) out of the users found in the Git history.
I can see this because there were Git-identities named "logonname <[email protected]>" when a user forgot to set its identity in the Git config.
Let's not say users/usernames are generated but "persons".
One users will appear multiple (at least two) times in the Persons page (this is what I've called users before). One user is reflected by the Crowd user, another by the developers git identity.
I don't think this is related to the Git nor the Crowd plugin but Jenkins.
Because there are multiple authentication and versioning plugins they shouldn't care about each other to solve this issue.
Jenkins should provide a mechanism to associate a VCS identity with Jenkins identity (optionally provided by an authentication plugin).