[JIRA] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

Mon, 22 Apr 2013 10:00:39 -0700

Joe Hansche commented on Improvement JENKINS-17693

Interesting... I see two potential issues here:

  1. The SSL exception seems to imply that your Confluence instance is requiring HTTPS, but the certificate can't be validated by the Jenkins server. Is your instance accessible via non-SSL (http:// only)?
    • If your server allows that, what happens if you change the URL in the Jenkins system configuration to remove the https requirement?
    • If your server requires HTTPS, then it will likely require importing the SSL certificate from the Confluence server into the Jenkins server's JVM. I've had to do this a couple times in the past, particularly with newer Certificate Authorities that weren't available (or weren't widely popular) at the time the JVM you use was released. If this is what's required, I will look up instructions for importing that certificate and see if it helps. On a side note, how many Jenkins servers are in your cluster? Because I believe all servers (master and slaves) will need to have the certificate imported in order to support this.
  2. It sounds like your Confluence instance does not have the remote APIs enabled, based on the "There is no SOAP service at this location
    " error.
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