Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
1.0-M3
-
Security Level: public (Regular issues)
-
None
Description
Ouch, this is a nasty one. If you deploy app Foo, then change it to be broken (invalid DD, whatever) and redeploy it, it goes like this:
1) undeploy old one
2) try to deploy new one
3) fail
The result is that the old one has been undeployed but the new one hasn't been deployed. It would be ideal if we could "try" the deploy operation first, and only if it appears valid, undeploy the old version and start the new version. I'm not sure how that could be done.