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

Wed, 23 Jan 2013 10:07:58 -0800

 
Trevor Baker edited a comment on Bug JENKINS-16383

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: [email protected]
Jabber notifier plugin: [ERROR] not connected. Cannot send message to '[email protected]'
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

Reply via email to