Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Extract resolvers into separate plugins to allow administrator to decide which resolvers to use.
Attachments
Issue Links
- depends on
-
JENKINS-15440 Emailing users at the end of a failed build very slow for big Jenkins instance using subversion
-
- Resolved
-
-
JENKINS-16389 Emailing users at the end of a failed build very slow for big Jenkins instance using CVS
-
- Resolved
-
- is blocking
-
JENKINS-16342 asynchPeople very slow when using Gravatar & Subversion plugins
-
- Resolved
-
-
JENKINS-14755 Mail address resolution can take a significant amount of time
-
- Resolved
-
- is related to
-
JENKINS-11990 After updating Active Directory plugin the Jenkins People database is experiencing massive performance issues synching because it is trying to authenticate users that are no longer in company Active Directory but are part of the Jenkins Database
-
- Open
-
I have to agree with @kutzi that having published plugins known to cause abysmal performance problems is not a good idea. Lots of people will just blindly install stuff and not read the warnings. Better to unconditionally delete bad code.
If there is a real use case for mail address resolvers that infer information from build records, then they should be written carefully to have reasonable performance. For example: