-
Bug
-
Resolution: Duplicate
-
Major
Various different SCM plugins implement MailAddressResolver, some of them have performance issues. It would be nice to find a good way to work around this.
- depends on
-
JENKINS-16437 Extract MailAddressResolvers to dedicated plugins
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-14755] Mail address resolution can take a significant amount of time
| Link |
New:
This issue is duplicated by |
| Link |
New:
This issue is duplicated by |
| Link |
New:
This issue is duplicated by |
| Link |
New:
This issue is duplicated by |
| Link |
New:
This issue is duplicated by |
| Link |
New:
This issue is duplicated by |
Deepak Panchal
added a comment - Also look at Issue JENKINS-14837
Jenkins version - 1.447.2
Email Ext Plugin version - 2.24.1
We are experiencing these very same symptoms (JIRA Issue 13700) just wanted to add some info that may be helpful in diagnosing the issue. We have seen jobs hang on the e-mail step on jobs configured for Base Clear Case, Clear Case UCM, TFS, as well as jobs that have no SCM component configured. The delay seems to be related to the number of email addresses the plug-in is attempting to send to. So large projects (largest number of developers) take the longest. Also as far as Jenkins is concerned the job is done so subsequent builds of the same jobs may kick off while the hung job is still spinning on another slave. Please let us know if any additional info will be helpful.
For what it's worth - I see this is marked as bug, but it is a blocker for us as we have a pretty large environment (60 slaves) and will cause us to go back a version. Thanks!
bbonn
added a comment - - edited Jenkins version - 1.447.2
Email Ext Plugin version - 2.24.1
We are experiencing these very same symptoms (JIRA Issue 13700 ) just wanted to add some info that may be helpful in diagnosing the issue. We have seen jobs hang on the e-mail step on jobs configured for Base Clear Case, Clear Case UCM, TFS, as well as jobs that have no SCM component configured. The delay seems to be related to the number of email addresses the plug-in is attempting to send to. So large projects (largest number of developers) take the longest. Also as far as Jenkins is concerned the job is done so subsequent builds of the same jobs may kick off while the hung job is still spinning on another slave. Please let us know if any additional info will be helpful.
For what it's worth - I see this is marked as bug, but it is a blocker for us as we have a pretty large environment (60 slaves) and will cause us to go back a version. Thanks!
Maybe you can provide a way to add a few ids to the ignore list so Jenkins doesn't send email to these predefined list of ids. eg. I see its trying to resolve an Ids called "VisualSVN Server" which will not exist but my build takes forever to finish.
INFO: No results found for filter sAMAccountName=VisualSVN Server inside baseDN ...