[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Andre Doherty commented on JENKINS-21863 WebSphere deployer: deploy to cluster @schaudhari : in case you haven't solved your issue yet, the problem you meet is connected to the mismatch of the certificate shown by your server and the url (console or soap (see serverindex.xml)) you used (128.0.1.212). As for me, i am trying to deploy an app on a server + an ihs web server at the same time, something that is feasible via the console. Is there some trick that allows to do it using the plugin ? Thank you 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/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
schaudhari schaudhari commented on JENKINS-21863 WebSphere deployer: deploy to cluster Hi I tried deploying EAR file to only cluster... got below error Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- E.ear --- Deploying New 'PORTAL_war' to IBM WebSphere Application Server Deploying to target: 'WebSphere:cluster=DevCluster1' Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to install artifact: Failure uploading archive to server at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.installArtifact(WebSphereDeploymentService.java:167) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.deployArtifact(WebSphereDeployerPlugin.java:201) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:178) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1701) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Build step 'Deploy To IBM WebSphere Application Server' changed build result to FAILURE Finished: FAILURE 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/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
schaudhari schaudhari commented on JENKINS-21863 WebSphere deployer: deploy to cluster After looking at logs I did found out this ... Caused by: com.ibm.websphere.management.filetransfer.client.TransferFailedException: Upload retry limit exceeded for file /var/lib/jenkins/jobs/Test-Websphere-Deployment/workspace/EX.ear. Exception: java.io.IOException: HTTPS hostname wrong: should be 128.0.1.212 at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFileInternal(FileTransferClientImpl.java:595) at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFile(FileTransferClientImpl.java:462) at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFile(FileTransferClientImpl.java:369) at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFile(FileTransferClientImpl.java:293) at com.ibm.ws.management.application.client.AppInstallHelper.copyToServer(AppInstallHelper.java:1245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.ibm.websphere.management.application.AppManagementProxy.uploadArchive(AppManagementProxy.java:718) ... 13 more Caused by: java.io.IOException: HTTPS hostname wrong: should be 128.0.1.212 at sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.java:529) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:454) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnectionOldImpl.connect(HttpsURLConnectionOldImpl.java:142) at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.connectToServer(FileTransferClientImpl.java:2947) at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.openConnection(FileTransferClientImpl.java:2859) at com.ibm.ws.management.filetransfer.client.FileTransferClientImpl.uploadFileInternal(FileTransferClientImpl.java:547) ... 22 more Is there any place where we give credentials for https hostname?? 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/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster Yes, i am using Apache in front of the application server and we deploy a new EAR each time. I unfortunatley don't know how to generate the application.xml file. 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/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster Thanks Leonardo for the explanation. I suppose that the plugin is working perfecly that way. For my problem, I talk about an IBM web server (Server Web Server on Websphere interface). That's why we need to give information about : the cluster for the deployment on WebSphere and also for the webserver. As i understand, the server field in the class correspond to an "applicative server". So if the cluster isn't empty, only cluster will be configured and the nodeserver will be disable. I am going to check the IBM api. Thanks ! 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Leonardo Costantini edited a comment on JENKINS-21863 WebSphere deployer: deploy to cluster Hi Nicolas, can you better describe your setup? are you using IHS (or ApacheHTTPD/IIS) plus Websphere Plugin in front of the application server? if yes, when deploying a new EAR or WAR within a EAR , than you must regenerate and propagate plugin configuration file. It will be automatically picked up after some min. This is needed both cluster or single server @Greg: This should be a standard behaviour in case of deployment both cluster or single server when using the WAS Plugin... If you think this can be done I think it is better to start a separate improvemnt ticket on this... do you agree? Regenerating and propagate the plugin confing file is done same way as the deployment (via admin console using IBM API) Ref: http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_pluginconfig.html https://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Frxml_plugin.html but there could be some other parameters to be passed to the deployed plugin (i.e the virtualhosts). If you nedd any info/support on this, just ask... if no and you just using the reverse proxy feature of web servers, than I think this is nothing to do with WebSpehre deploy plugin... @Greg: do you agree? any clue which can be a proper plugin candidate for this? Best Regards, Leonardo 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Leonardo Costantini commented on JENKINS-21863 WebSphere deployer: deploy to cluster Hi Nicolas, can you better describe your setup? are you using IHS (or ApacheHTTPD/IIS) plus Websphere Plugin in front of the application server? if yes, when deploying a new EAR or WAR within a EAR , than you must regenerate and propagate plugin configuration file. It will be automatically picked up after some min. This is needed both cluster or single server @Greg: This should be a standard behaviour in case of deployment both cluster or single server when using the WAS Plugin... If you think this can be done I think it is better to start a separate improvemnt ticket on this... do you agree? Regenerating and propagater the plugin confing file is done same way as the deployment (via admin console using IBM API) Ref: http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_pluginconfig.html https://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Frxml_plugin.html but there could be some other parameters to be passed to the deployed plugin (i.e the virtualhosts). If you nedd any info/support on this, just ask... if no and you just using the reverse proxy feature of web servers, than I think this is nothing to do with WebSpehre deploy plugin... @Greg: do you agree? any clue which can be a proper plugin candidate for this? Best Regards, Leonardo 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Leonardo Costantini edited a comment on JENKINS-21863 WebSphere deployer: deploy to cluster Hi Nicolas, can you better describe your setup? are you using IHS (or ApacheHTTPD/IIS) plus Websphere Plugin in front of the application server? if yes, when deploying a new EAR or WAR within a EAR , than you must regenerate and propagate plugin configuration file. It will be automatically picked up after some min. This is needed both cluster or single server @Greg: This should be a standard behaviour in case of deployment both cluster or single server when using the WAS Plugin... If you think this can be done I think it is better to start a separate improvemnt ticket on this... do you agree? Regenerating and propagate the plugin confing file is done same way as the deployment (via admin console using IBM API) Ref: http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_pluginconfig.html https://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Frxml_plugin.html but there could be some other parameters to be passed to the Jenkins deployer plugin (i.e the virtualhosts). If you nedd any info/support on this, just ask... if no and you just using the reverse proxy feature of web servers, than I think this is nothing to do with Jenkins WebSphere deployer plugin... @Greg: do you agree? any clue which can be a proper plugin candidate for this? Best Regards, Leonardo PS we start speaking of two different plugins: the IBM WAS plugin and the Jenkins WebSphere Deployer plugin... risk of confusion is high... I propose to refer first as WAS plugin and second as JWD plugin... just to make difference! what do you think? 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster Hi, We are also looking for the release of this patch. I looked in your code, and it seems that, if i amn't wrong, you just need to add the parameter in the constructor, add the getter/setter and call for service.setTargetCluster( cluster ) (and also the input text in the other class for the form). I didn't try it as I don't have any ide right now on my computer. In any case, thanks for your work. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters updated JENKINS-21863 WebSphere deployer: deploy to cluster Attached is the beta version for clustering. Please manually install this .hpi to replace your current version. Let me know the results and I'll release a new version with clustering support so others can benefit from it. Change By: Greg Peters (04/Mar/14 4:42 PM) Attachment: websphere-deployer.hpi 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster That's a quick answer ! I will try it right now. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters resolved JENKINS-21863 as Postponed WebSphere deployer: deploy to cluster Postponing development progress until feedback on the attached file is given. Change By: Greg Peters (04/Mar/14 4:43 PM) Status: InProgress Resolved Resolution: Postponed 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster I don't know if i made a mistake during the install of the plugins, but i have this error during the build. FATAL: com/ibm/websphere/management/AdminClientFactory java.lang.NoClassDefFoundError: com/ibm/websphere/management/AdminClientFactory at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.connect(WebSphereDeploymentService.java:234) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.connect(WebSphereDeployerPlugin.java:271) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:173) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClientFactory at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(Unknown Source) ... 12 more 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue edited a comment on JENKINS-21863 WebSphere deployer: deploy to cluster EDIT As i remember, i had to add the ibm librairies inside. I will retry. I don't know if i made a mistake during the install of the plugins, but i have this error during the build. FATAL: com/ibm/websphere/management/AdminClientFactory java.lang.NoClassDefFoundError: com/ibm/websphere/management/AdminClientFactory at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.connect(WebSphereDeploymentService.java:234) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.connect(WebSphereDeployerPlugin.java:271) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:173) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClientFactory at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(Unknown Source) ... 12 more 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters commented on JENKINS-21863 WebSphere deployer: deploy to cluster I'm not sure what EE container your using, but if you're using Tomcat, the plugin will be found in ../webapps/jenkins/WEB-INF/plugins This is the directory where the plugin should be replaced. If you click "Test Connection" it will tell you where the libraries are suppose to be placed. You shouldn't have to replace the IBM WebSphere libraries so that error is a little puzzling to me. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster I solve the problem by adding the 2 ibm jar (com.ibm.ws.runtime_6.1.0.jar and com.ibm.ws.admin.client_6.1.0.jar) in the lib directory of the plugin. Jenkins doesn't know the ibm class as websphere in on another server. After a successful build, the result isn't perfect yet for our case. Only the cluster is configured : Module Web WebSphere:cell=CELLNAME,cluster=CLUSTERNAME On the previous version of the plugin we had : WebSphere:cell=CELLNAME,node=NODENAME,server=SERVERNAME Expected result is : WebSphere:cell=CELLNAME,cluster=CLUSTERNAME WebSphere:cell=CELLNAME,node=NODENAME,server=SERVERNAME I don't know if it is a standard Websphere configuration and if everybody needs this kind of conf. I am a new on Websphere, i always work with tomcat environnement. Thanks a lot for your work. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue edited a comment on JENKINS-21863 WebSphere deployer: deploy to cluster I solve the problem by adding the 2 ibm jar (com.ibm.ws.runtime_6.1.0.jar and com.ibm.ws.admin.client_6.1.0.jar) in the lib directory of the plugin. Jenkins doesn't know the ibm class as websphere is on another server. After a successful build, the result isn't perfect yet for our case. Only the cluster is configured : Module Web WebSphere:cell=CELLNAME,cluster=CLUSTERNAME On the previous version of the plugin we had : WebSphere:cell=CELLNAME,node=NODENAME,server=SERVERNAME Expected result is : WebSphere:cell=CELLNAME,cluster=CLUSTERNAME WebSphere:cell=CELLNAME,node=NODENAME,server=SERVERNAME I don't know if it is a standard Websphere configuration and if everybody needs this kind of conf. I am a new on Websphere, i always work with tomcat environnement. Thanks a lot for your work. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters commented on JENKINS-21863 WebSphere deployer: deploy to cluster I'm confused. Did it deploy to successfully? Are you asking me to disable the "node" "server" on the config page if you choose to deploy to a cluster? 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster No the contrary. I configured on jenkins : node, cell, server, cluster. After the build, i can only see on websphere : Module Web WebSphere:cell=CELLNAME,cluster=CLUSTERNAME It is like the server name node are disable as you said. The result is that i can go to my application by accessing with IP adress, but i can't with my domain name as the apache server isn't configured. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters updated JENKINS-21863 WebSphere deployer: deploy to cluster Try this version out. Look in the jenkins log for a new line "Deploying to target...". Let me know what that says. Then let me know what you expect it to say. Change By: Greg Peters (04/Mar/14 6:05 PM) Attachment: websphere-deployer.hpi 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
nicolas delrue commented on JENKINS-21863 WebSphere deployer: deploy to cluster Thanks, I can't do it right now, but i will try tomorrow. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Leonardo Costantini commented on JENKINS-21863 WebSphere deployer: deploy to cluster Thanks Greg, faster than light... I test ASASP (honestly I didn't expectes a so quick answer... so thanks twice!) One question, will the deploy on cluster operation trigger also a ripplestart or should this be done with another step ad-hoc? @Nicolas yes only cluster is needed: in WebSphere Network Deployment, a cluster is composed of many servers on many nodes. If you deploy on a cluster, you cannot specify which servers (thus which nodes), as every server on the cluster must have the very same version of the aplication installed. Instead, if you deploy on a single server, than you must specify on which node it resides Best Regards, Leonardo 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Leonardo Costantini edited a comment on JENKINS-21863 WebSphere deployer: deploy to cluster Thanks Greg, faster than light... I test ASASP (honestly I didn't expect a so quick answer... so thanks twice!) One question, will the deploy on cluster operation trigger also a ripplestart or should this be done with another step ad-hoc? @Nicolas yes only cluster is needed: in WebSphere Network Deployment, a cluster is composed of many servers on many nodes. If you deploy on a cluster, you cannot specify which servers (thus which nodes), as every server on the cluster must have the very same version of the aplication installed. Instead, if you deploy on a single server, than you must specify on which node it resides Best Regards, Leonardo 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters commented on JENKINS-21863 WebSphere deployer: deploy to cluster Thanks Leonardo. Frankly, I'm not sure how the plugin will react to cluster support. Since the plugin is directly connected to only one server instance, I don't believe it will propagate the stop, uninstall and install to the other instances in the cluster. I'm not even sure if you can ripplestop/rippleuninstall/rippleinstall/ripplestart through one connection. I'm not versed on ND so feel free to educate me. Keep me up to date on your testing progress. 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters started work on JENKINS-21863 WebSphere deployer: deploy to cluster Change By: Greg Peters (25/Feb/14 8:08 PM) Status: Open InProgress 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters assigned JENKINS-21863 to Greg Peters WebSphere deployer: deploy to cluster Change By: Greg Peters (25/Feb/14 8:08 PM) Assignee: GregPeters 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Greg Peters commented on JENKINS-21863 WebSphere deployer: deploy to cluster Can you confirm that cluster and cell are the only required inputs? 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Leonardo Costantini commented on JENKINS-21863 WebSphere deployer: deploy to cluster Actually only cluster should be needed You can have a look to http://websphereapplicationservernotes.wordpress.com/2012/12/25/wsadmin-tutorial-part2/ http://www.webspheretools.com/sites/webspheretools.nsf/docs/jacl%20script%20to%20deploy%20ear%20file http://wsadminlib.blogspot.it/2010/05/how-to-install-application.htmlhttp://wsadminlib.blogspot.it/2010/05/how-to-install-application.html http://www.websphere.pe.kr/xe/?document_srl=3861mid=was_wsadminsort_index=regdateorder_type=asc after an application is deployed on a cluster environment a rollout update take place (a node sync and after that a restart of the servers of the cluster, one at time) I expect your plugin invoke wsadmin client... 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.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
leonardo Costantini created JENKINS-21863 WebSphere deployer: deploy to cluster Issue Type: Improvement Assignee: Unassigned Components: websphere-deployer Created: 18/Feb/14 10:22 PM Description: At the moment the plugin can deploy application to single servers Improvement request is to add cluster name as option for application deployment. chosing cluster, the node and server options should be disabled Project: Jenkins Labels: plugin Priority: Minor Reporter: leonardo Costantini 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.
