[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
Jesse Glick commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins For the record, my proposal was to delete the known plugins implementing MailAddressResolver poorly, not to delete the extension point itself which is not inherently harmful. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
Oliver Gondža commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins Well, lets try to delete it. https://github.com/jenkinsci/mailer-plugin/pull/6 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
Jesse Glick commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
kutzi commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins I'm fine if you want to do this. I just want to explain my opinion a bit more: we should have the courage to delete 'bad' code and not keep it forever just because of the vague suspicion that someone somewhere might still use it the 'danger' (and I agree it's debatable if that's a danger) of having these plugins around is, that someone might discover them, think they're useful and use them and than later complain about the performance issues or other stuff in them 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
Oliver Gondža commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins I do not dare to say they should be deleted, but I do not see much value using them either. All I want is SVN and CVS without resolver. Maintaining a couple of dead one-file plugins is a workload I can handle. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
kutzi commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins I've the opinion that the resolvers should be deleted instead of extracted - at least for SVN and CVS. Not sure if there are implementations in other SCM plugins and if those are using equally deprecated SCM repositories. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
Oliver Gondža updated JENKINS-16437 Extract MailAddressResolvers to dedicated plugins Change By: Oliver Gondža (24/Jan/13 12:26 PM) Component/s: mail 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
[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins
Oliver Gondža created JENKINS-16437 Extract MailAddressResolvers to dedicated plugins Issue Type: Improvement Assignee: Unassigned Components: plugin Created: 22/Jan/13 11:16 AM Description: Extract resolvers into separate plugins to allow administrator to decide which resolvers to use. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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
