Reza, that is the correct configuration path syntax. Is there not a "lastSuccessful" directory under the "test" job specified in your file system? What's the path of the test.ear that's built?

there is no lastSuccessful directory in under the "test" directory within the job folder.
When I kick of the build in Jenkins, the ear files are being archived here for example:

D:\Program Files\Jenkins\jobs\test\modules\<another_directoy>\builds\2013-01-18_13-25-30\archive\<another_directory>\test\1.1

I put **/test.ear as the value of ear path as suggested in the documentations. Am I missing something?

Reza, This is a bug that's currently being worked on (there is no workaround at this time). Please provide the OS name & version that's running Jenkins. Also provide the version of Jenkins. Please expect ~2 weeks for the update.

Also, reference https://issues.jenkins-ci.org/browse/JENKINS-17681 for the lastSuccessful issue under Windows. You must have a "lastSuccessful" symlink that points to "build/lastSuccessfulBuild" in order for the plugin to find the correct path.

jenkins:1.532
OS: Windows Server 2k8 R2

Reza, you can try the following EAR path to see if it works for you.
"../../modules/**/test.ear" or "../modules/**/test.ear" (without quotes)

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, but 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.

Hi,

We are facing the same issue too. We have tried on Windows 7 and Windows 2003 Server. The latest suggestion from Greg on 20th December 2013 did not help us.

Please help.

Also, we are observing other issues which I will raise as a separate bugs. Below is the summary of them.

• SOAP Connector Port value not getting persisted in the configuration after Save operation on the Job. (Updated value does not show up on the form but Test Connection picks up the updated value)
• Once the Test Connection is successful for a server, we cannot establish connection to another server EVEN in other job. It says 'Already Exists!' when we provide other server details and use Test connection.

Thanks in advance