Jenkins全新部署使用容器部署插件，但如果重新部署则失败

Question

I want to set up my maven built web app, to build and deploy as part of my regular job.

The build works fine, however using the container deployment plugin seems unreliable in that a fresh deployment works but redeploying the app fails. The plugin can not deploy when app is already deployed (the war is already in webapps directory). To be clear if I delete the war's and undeploy everthing and then to a jenkins build it works as expected but then subsequently they fail. The error message is :

org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Encountered exception javax.management.RuntimeErrorException: Error invoking method check

Should I instead be deploying as part of the maven build itself, using deploy:deploy and adding a distribution management section ?

Or is their a jenkins setting i am missing ?

Answer 1

Had just the same issue. Surprisingly, completely other things helped in my case.

Looked at tomcat logs at redeploy time, and saw OutOfMemory: Permgen space . Increasing XX:PermSize and XX:MaxPermSize to 256m in $CATALINA_HOME/bin/setenv.sh solved this issue completely.

Answer 2

Might also happen if you try to deploy 2 apps with the same context root in context.xml (but another defined in jenkins when deploying).

Had to manually clean /webapps and restart the server. Works again now.

Answer 3

Firstly, maven deploy plugin does not deploy a web application to a container. It deploys the project artifact to a maven repository. So, it cannot be used for your purpose.

Secondly, refer to this related open jira issue. This also suggests a solution/workaround.

Answer 4

before you deploy the war file you can undeploy the existing package by using this. http://mojo.codehaus.org/tomcat-maven-plugin/undeploy-mojo.html I think you can add this task in the same job before you do the deployment.So you can still have CI as you are expecting.

Answer 5

I am doing this https://stackoverflow.com/a/6524012/106261

I can either call cargo:redeploy as a post build step if I want to have deployment detail stored within pom

Or I call cargo:undeploy as a post build step, then use container deploy plugin to actually deploy using the settings I put in jenkins.