I'm having this exact same problem. Was a workaround ever found?

Jenkins 1.574 / Tomcat 7.0.55 / JRE 1.7.0_60 / Deployer 1.10

I think this is a more subtle issue may actually be a Cargo issue (haven't checked the bugs there).

I was able to deploy a WAR file with the name appName##NN.war (where NN is constructed from the BUILD_NUMBER) once. I accomplished this by using the following Ant glob pattern for the WAR/EAR file:

*/.war

I left the context path blank, and I made sure to not include a context.xml with a path attribute.

However, the second attempt (the actual parallel deployment) failed with:

ERROR: Publisher hudson.plugins.deploy.DeployPublisher
aborted due to exception
org.codehaus.cargo.container.ContainerException:
Failed to undeploy /home/tcadmin/.jenkins/jobs/ConsumeIT-Deploy/workspace/target/ConsumeIt##14.war

Once I undeployed the application from the remote Tomcat, I could then successfully run another Maven deploy job, which incremented the BUILD_NUMBER.

I can post the entire stack trace if needed.

First of all, the entire point of doing a parallel deploy is to avoid undeploying a live application.

Second of all, the undeploy command needs to be instrumented in order to handle versions (/manager/text/undeploy?context=ConsumeIt&version=14)

While Cargo's performUndeploy for Tomcat7x overrides the stock method, the Javadoc doesn't mention versions.

getPath and getVersion explicitly mention version support.

My initial reaction is that the Tomcat7xRemoteDeployer Cargo class needs to recognize that it's dealing with a versioned WAR file and not attempt to undeploy.

For the undeploy command, there needs to be an optional version component.

It appears that Tomcat8xRemoteDeployer suffers from the same issue.

Looks like the issue is fixed in a newer version of Cargo (see https://codehaus-cargo.atlassian.net/browse/CARGO-1041), but the plugin would need be updated.

this should be fixed since v1.10

I'm still having this problem with plugin version 1.15.

[DeployPublisher][INFO] Deploying /mnt/cluster/build/jobs/DF Collection Agent Renewal/jobs/Deploy to PROD/workspace/build/libs/df#collection##1005.war to container Tomcat 7.x Remote with context null
Redeploying .../df#collection##1005.war
Undeploying .../df#collection##1005.war
ERROR: Build step failed with exception
org.codehaus.cargo.container.ContainerException: Failed to undeploy .../df#collection##*1005*.war
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.undeploy(AbstractTomcatManagerDeployer.java:136)

Hi gays, any hope for this plugin to support parallel deployment, i still can't redeploy a different version of same war

faroukosama I worked around this issue by deploying using a shell script that curl'd the war to tomcat.

I'd tag the source repo with a version tag. Parameterize the build with the tag and build the war from the selected tag.

Then configure the build so it can accept a war name and suffix the war name with the build number instead of the version number.

Since every build will have a greater build number, any subsequent builds will replace previous ones, and you can easily roll back to previous version tags if needed.

wkbaran Yes dear, this is the solution I'm using currently, i just wanted to make sure there is no fix done for this plugin, so i use it