[
https://issues.jenkins-ci.org/browse/JENKINS-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160322#comment-160322
]
Rob Petti commented on JENKINS-13103:
-------------------------------------
I believe the active directory provider in jenkins also provides a mail
resolver, so if it's defined in active directory then it obtains it from there.
If it's not, then it moves on to other mail resolvers, including the one
provided by the perforce plugin.
JENKINS-12952 looks like it describes the same issue. The fix was released in
perforce plugin 1.3.10, so I'd recommend upgrading to that and trying again.
> Build hangs trying to send email if an email address isn't defined in Active
> Directory
> --------------------------------------------------------------------------------------
>
> Key: JENKINS-13103
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13103
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Jenkins - 1.455
> email-ext 2.18
> perforce plugin - 1.3.9
> AD plugin - 1.26
> Windows 2003 master
> Linux x64 slave
> Reporter: aflat
>
> I think the hang is due to the email-ext plugin, but there may be a perforce
> plugin issue as well.
> https://issues.jenkins-ci.org/browse/JENKINS-13102
> What I don't understand is why is the perforce plugin asking for the email
> from Active directory? The email is defined in perforce, shouldn't it just
> use that when creating the email list?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
