|
||||||||
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 ... bloom...@java.net (JIRA)
- [JIRA] (JENKINS-13788) Git user and Cro... t.lehm...@strato-rz.de (JIRA)
- [JIRA] (JENKINS-13788) Git user and Cro... t.lehm...@strato-rz.de (JIRA)
- [JIRA] (JENKINS-13788) Git user and Cro... michelj...@java.net (JIRA)
Hi!
I think I have run into the same problem as the creator of this issue. We have a setup with Stash/Git, Crowd and Jenkins. When logging into Jenkins, Jenkins checks the credentials with Crowd and if it is a new user, Jenkins creates a user. When doing so, it uses the full name + username from Crowd, e.g. 'Anders Jacobsson (netjaan)', as the user id. However, this is obviously not the same as what is configured for git, i.e. user.name = netjaan. This results in Jenkins not being able to match commits with already existing users (there is another bug, JENKINS-14250, that is also related to this).
My guess is that the problem is in the Crowd plugin and not in the Git plugin.