Someone filed something on this as JENKINS-13715, did you ever come up with a resolution?
slide On Tue, May 17, 2011 at 6:44 AM, Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote: > Well, I did find the cause of this problem in the end. > > The list of people in jenkins/people/ is populated by parsing the > changelog.xml's (see the method View.People.getUserInfo(...)). > > Now, in addition to our SVN repository, we also have some Git repositories. > Some of these are git-svn clones, where the author meta looks like this > (it's the default behavior for git-svn to generate this email address): > > author t.nicolaisen <t.nicolaisen@901b3fc1-1df5-aa1e-233f-0cced8b7b346> > 1302777659 +0000 > > So, in the end the problem is that we have changelogs with bogus e-mail > addresses in the author tags. > > One solution could be to do git-svn with authormaps, and rewrite our git-svn > clones to have proper e-mail addresses that will also work in Jenkins. > However, this will be a big load of work for something that isn't really > useful for our git-svn repositories anyway. > > At the same time, I think it is weird that an e-mail address that is found > in the changelog of a Git repository, is used for notification in a build > that is only using SVN, just because the usernames are the same in both > repositories. > > Also, when I manually change the email-address in the People configure page, > it reverts to the bogus email from the git-svn repository upon the next time > I load the people list. I think that if I specify an email address manually, > it should have precendence over whatever is parsed out of some changelog. > > Then again, I doubt anyone else are affected by this problem. Oh well, at > least it's google-able now ;) -- Website: http://earl-of-code.com
