1 answer
Hey Bunty!
It looks like from the logs that what you've posted is from Jenkins' application log (and not Jira's). Upfront I do want to set your expectations that we don't have a lot of Jenkins expertise since we have a competing offering for Server deployment called Bamboo, but I will try to troubleshoot this for you nonetheless!
The error in the log relates to not being able to verify an SSL certificate. Usually this happens because either the certificate is self-signed, or the Certificate Authority isn't trusted by Java by default. GoDaddy in particular is infamous for not being in the Java 7 security store, so particular certs purchased through GoDaddy will throw this error with older Java applications.
Is Jira by chance using a self-signed cert or one potentially purchased through godaddy?
One way you can test this (if your Jira server is exposed to the internet) is checking your instance with SSL Labs. There's a section in the results for various Java clients. If you get something like "Server closed connection" for the Java version your Jenkins application is running under, that would indicate a problem with your certificate trust.
If this is what's happening, you'll want to add your Jira certificate to your Jenkins keystore. This sounds like it might be the opposite direction of what you've already done. Without knowing the particulars of your Jenkins setup (and again, I'm not a Jenkins expert) it will be difficult to guide you with this part. But more or less it should be fairly similar to adding certs to Jira's keystore, just with different certificates and file paths. This thread goes over adding certs to a specific Jenkins install if you need a little guidance.
Hope that helps!
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.