Jesse Glick commented on Improvement JENKINS-16437

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:

  • require the user to specify a sample job or jobs, rather than searching every job in the Jenkins installation
  • inspect only up to some maximum number of build records per job (with lazy loading this is especially critical)
  • cache information obtained from such searches, e.g. using the Database plugin, so you have only a one-time hit
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to