[JIRA] (JENKINS-16383) add option for SSL connection instead of SASL

[trba...@adobe.com (JIRA)]

Trevor Baker edited a comment on JENKINS-16383 add option for SSL connection instead of SASL Yes, I have tried, and it fails to connect and does not log anything connection related at all, despite having set the log level to FINEST for hudson.plugins.jabber If I specify a bogus port and click apply I see "Unable to connect to im.corp.adobe.com:5229 : Connection refused: connect" back to the screen, but nothing ever ends up in the logs. The only plugin related logging I can see is the following when no "server" is provided: Jan 23, 2013 11:57:03 AM hudson.plugins.jabber.im.transport.JabberPublisherDescriptor configure INFO: No hostname specified. A job that has the notifier enabled as a post build action shows the following in the build log, but still nothing to the Jenkins log: Jabber notifier plugin: Sending notification to: r...@conference.mycorp.com Jabber notifier plugin: [ERROR] not connected. Cannot send message to 'r...@conference.mycorp.com'

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