|
||||||||
|
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.
Reza, you can try the following EAR path to see if it works for you.
"../../modules/*/test.ear" or ""../modules/*/test.ear"
Remote Deployment to WebSphere *New Requirements*
First, you'll need to import the DummyClientTrustFile.jks from WebSphere into your "cacerts" trust store in the JDK that jenkins is running under. The path is typically jre/lib/security/cacerts
Lastly, if you are deploying remotely to WebSphere, you may need to include the hostname and IP of the Solaris box in Windows "etc/hosts" file. Since Windows needs to resolve the DNS (This my not be needed, put add it if you're unsure)
I've identified the fix on my end so the above workaround may work for you until I get the next release out.