Problems with E-mail notification: Recipient host is svn uuid instead of Default user e-mail suffix

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems with E-mail notification: Recipient host is svn uuid instead of Default user e-mail suffix

Thomas Ferris Nicolaisen-2
Hi,

We are running Jenkins 1.405 in tomcat 6.0.29 on debian 5.0.8. Java 1.6.0_22.

Normal email notification works fine, but if we check the "Send separate e-mails to individuals who broke the build" option, the normal host suffix becomes some key from svn. This is the console output at the end of a build:

[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 41 seconds
[INFO] Finished at: Thu Apr 14 10:33:05 CEST 2011
[INFO] Final Memory: 33M/242M
[INFO] ------------------------------------------------------------------------
channel stopped
Sending e-mails to: t.nicolaisen@901b3fc1-1df5-aa1e-233f-0cced8b7b346
Finished: SUCCESS

The suffix there is our svn repository uuid, specifically the value in the file svn_server/db/uuid 

The next thing that happens is that, naturally, the Jenkins admin email account gets a failure notice from our mail server, saying: 

Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=901b3fc1-1df5-aa1e-233f-0cced8b7b346.ourcompany.de type=A: Host not found

Jenkins is configured with "Default user e-mail suffix": @ourcompany.de

Our Jenkins installation has been through many upgrades (all the way back since hudson 1.270'ish).

I've tried recreating locally on OS X with the same tomcat, jenkins version, and same mail server configuration, but there the notification works perfectly.

I'm not sure what triggered the problem, but this did work fine in the past. We did recently upgrade from Hudson 1.396 to Jenkins 1.405.

I think this has more to do some rusty old configuration in JENKINS_HOME, but I can't figure out what. Contents of hudson.tasks.Mailer.xml looks OK.

I'd hate to have to set up our Jenkins from scratch, so I would really appreciate if anyone has some ideas I can try out.

Thanks in advance for all pointers!

-Thomas
Reply | Threaded
Open this post in threaded view
|

Re: Problems with E-mail notification: Recipient host is svn uuid instead of Default user e-mail suffix

Thomas Ferris Nicolaisen-2
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 ;)
Reply | Threaded
Open this post in threaded view
|

Re: Problems with E-mail notification: Recipient host is svn uuid instead of Default user e-mail suffix

slide
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
<[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: Problems with E-mail notification: Recipient host is svn uuid instead of Default user e-mail suffix

Dennis Hartrampf
This post has NOT been accepted by the mailing list yet.
Four years later and now we are facing the same problem in the company I work for.
We migrated from SVN to Git. We used the SVN-Git-bridge and now have git-svn repositories.

Jenkins updates the host-part of the mail adresses of our users with the uuid of the svn repositories. This only happens for users that have not registered themselves in our Jenkins but where registered by Jenkins itself (because their names apper in svn resp. git logs).

We too have been using Jenkins for a long time now, updating from version to version.

Can you give some advice on how to avoid this problem?