This appears to be the following issue:
https://issues.jenkins-ci.org/browse/JENKINS-19564
My initial take on this is that it's a Cargo issue with parallel deployment.
Mark
/mde/
On Monday, August 4, 2014 6:23:40 PM UTC-7, Mark Eggers wrote:
>
> Further followup:
>
> It seems that the Deploy pl
Further followup:
It seems that the Deploy plugin doesn't work well with versioned WAR files
(ConsumeIt##nnn.war). The first deploy works as expected, and the second
deploy (with an incrementally increased BUILD_NUMBER) fails with:
Deploying
/home/tcadmin/.jenkins/jobs/ConsumeIT-Deploy/workspa
Never mind, I figured it out. It turns out that the deploy URL in the
configuration needs to be the base URL (http://thor.mdeggers.org:8080), and
NOT the manager URL (http://thor.mdeggers.org:8080/manager/text).
Now I have to figure out how to filter context.xml so that I can run the
applicatio
Hi,
I'm trying to use the deploy plugin to deploy to a Tomcat 7.0.55 server.
I'm trying to use versioned WAR files (appName##number.war).
I can create the WAR file easily by passing BUILD_NUMBER in on the command line
and then using a property within finalName.
The first problem came when specif
