-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
undeploy-like tasks dependencies #164
Comments
I don't think you need to necessarily create the underlying artifact deployable to undeploy. You can probably just set the |
I've tried this:
Nevertheless, I'm getting this error message:
|
I've also tried this:
I'm getting this exception message:
My
|
Can you provide a stack trace? If that checks the existence of the |
This is the
And this is the task configuration:
|
@bmuschko have you been able to get something...? |
Hi, Facing the same issue with CargoUndeployRemote. For some reason it needs the exact war file name that's deployed on Tomcat. According to Tomcat documentation here: https://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Undeploy_an_Existing_Application That should not be required as the manager API only needs the action name (undeploy) and the context ('/', '/exeamples', etc.). Here is the error message: org.codehaus.cargo.container.ContainerException: Deployable [/ol-1.0.118] is not deployed For us knowing the exact war file name will not be possible anyway as the build process adds a suffix to the war file name indicating the Jenkins build number and the deployable is always built before the deployment task. Since builds do fail (sometimes) the indexes will be a bit out of sequence in those cases (i.e. 112, 113, 118 (because 5 builds failed in a row)). Here is my gradle script doing the undeploy. class RemoteContainer { def remoteContainers = [new RemoteContainer(name: 'devtest', hostname: 'testhost', remoteContainers.each { config -> class SafeUndeployRemote extends com.bmuschko.gradle.cargo.tasks.remote.CargoUndeployRemote {
} Any help regarding this would be much appreciated. Been stuck on this now for a while and would ideally like to keep things in Gradle (I know it can get it done with curl). |
I'm facing up how to deal with my
undeployDev
-like tasks.This is my configuration:
As you can see on my
undeployDev
-like task, it depends on another taskcreateDevelopmentWar
. So I don't want each time I need to undeploy the artifact, it needs to regenerate the deployable. I'd like to set which context the task need to undeploy without any other dependency.I've took a look on documentation, nevertheless, I don't quite figure what would I need to do...
The text was updated successfully, but these errors were encountered: