使用jenkins无法在tomcat中成功部署war文件 [英] Cannot successfully deploy war file in tomcat using jenkins

查看:399
本文介绍了使用jenkins无法在tomcat中成功部署war文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在 https 访问的服务器中安装了 tomcat 7.0.39 。我已成功部署并正在访问 jenkins v1.575 。我为jenkins使用SVN来检出我的 grails 项目的最新副本,并在运行tomcat的服务器上构建和部署它。我还安装了 Deploy Plugin ,让jenkins可以在容器中部署war文件。

I have tomcat 7.0.39 installed in a server accessed via https. I have successfully deployed and currently accessing jenkins v1.575. I am using SVN for jenkins to checkout the latest copy of my grails project, build and deploy it in the server where tomcat is also running. I have also installed the Deploy Plugin to make it possible for jenkins to deploy war file in a container.

是生成后的操作:

创建一个新的构建是成功的,但是每当jenkins尝试部署其构建的war文件时,我都会收到这个错误。

Creating a new build was successful, but whenever jenkins is trying to deploy its built war file, I am getting this error.

|Done creating WAR target/doe-lubes-0.1.war
Deploying /var/www/tomcat/.jenkins/jobs/doe-lubes/workspace/target/doe-lubes-0.1.war to container Tomcat 7.x Remote
ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception
org.codehaus.cargo.container.ContainerException: Failed to redeploy [/var/www/tomcat/.jenkins/jobs/doe-lubes/workspace/target/doe-lubes-0.1.war]
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:193)
    at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73)
    at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
    at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
    at hudson.FilePath.act(FilePath.java:922)
    at hudson.FilePath.act(FilePath.java:895)
    at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
    at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61)
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736)
    at hudson.model.Build$BuildExecution.post2(Build.java:183)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685)
    at hudson.model.Run.execute(Run.java:1765)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:234)
Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names present
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
    at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
    at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
    at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
    at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
    at sun.security.ssl.Handshaker.processLoop(Unknown Source)
    at sun.security.ssl.Handshaker.process_record(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
    at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:534)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.list(TomcatManager.java:686)
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.getStatus(TomcatManager.java:699)
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:174)

我找不到合适的解决方案因为我对詹金斯还是一个新手,所以对此我一一介绍。我可以手动成功地在tomcat中部署war文件,但是使用jenkins,我不能。
我需要配置什么来解决这个问题?

I cant find the right solution and walkthrough for this since I am still new to jenkins. I can successfully deploy war files in tomcat manually, but using jenkins, I can't. What do I need to configure to fix this?

谢谢。

推荐答案

将您的tomcat URL从https更改为http将解决此问题。我猜你的tomcat服务器并不真正在https中运行。

Changing your tomcat URL from https to http will fix this problem. I guess your tomcat server isn't really running in https.

这篇关于使用jenkins无法在tomcat中成功部署war文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆